Develop Bugs

[Q]Soft Brick boots to development warning screen

DISCLAIMER: I'm completely lost, so please break things down into bite-size steps or at least expect some follow-up questions on my part. I'm one of those desperate guys who is attempting to just have a working phone tomorrow. Any help will get as many presses of the thank button as I can possible give.
After several hours of plodding and poking and searching I've managed to do some possibly irreparable damage to my htc one v. Whenever I try to boot the phone it starts up with the htc developer red text "development use only" etc etc. I can access the bootloader and recovery thankfully, so I guess there's hope.
I think the source of my troubles is what's addressed by the essential reading at the top of this sub-forum, ie distinguishing between GSM and CDMA. I think (and this is an assumption here) that despite being in the USA on virgin, the fact that I can shove a sd-card in there means it's GSM (correct me if I'm wrong. please). EDIT: It seems that the phone only works with the CDMA version of TWRP, so I guess that might be an indicator.
Info: htc one v, virgin USA, using TWRP 2.3.3.0, attempted to flash Rom using various versions of Paranoid Android
What I've done thus far:
1. Unlocked bootloader
2. Flashed recovery
2.5. Created backup
3. rooted device (I downloaded rootchecker or somesuch app and was able to confirm that I had rooted my device)
4. Wiped cache and dalvik cache (I think that's what it's called).
5. Attempted to do a factory reset (failed).
6. Attempted to flash ROM (failed)
7. Restarted Device (got stuck on dev screen for the first time).
8. Tried recovering using backup created earlier (which just booted me into the dev screen of doom again).
9. Tried partitioning sd card in an attempt to perform a factory reset (wiped everything including backup).
10. Factory Reset failed with a message about not being able to mount /sd-ext.
11. Tried flashing rom again with different version of PA for shiggles (it worked! oh frabjous day!)
12. Rebooted phone only to get stuck on the dev screen again.
Guides I've used/perused/glanced at:
1. http://forum.xda-developers.com/showthread.php?t=2154635
2. http://forum.xda-developers.com/showthread.php?t=1598964
3. http://www.idroidspace.com/jelly-bean-4-2-2-paranoid-android-custom-rom-for-htc-one-v/
4. http://techmell.net/android-tips/ho...paranoid-android-4-1-2-jelly-bean-custom-rom/
5. http://androidlegend.com/upgrade-ht...ing_wp_cron=1369722527.0674550533294677734375
6. http://www.youtube.com/watch?v=a3pof_WSEEI
I've been at this for nigh on 7 hours and all I have to show for it is a phone I can't use. Help.

Let's try this in order: if you are with Virgin Mobile, it is a CDMA. GSM phones take a sim card, both versions accept an sd card for storage.
Everything looks good until:
#5 The failed warning is due to lack of a SD EXT partition on your sd card. If you didn't re-partition it, you will get that failed warning. No big deal as it is wiping everything else correctly.
#6 You also need to wipe system prior to flashing your new rom.
After flash your new rom, you will need to connect to your pc and boot into bootloader. Make sure it says "Fastboot USB" at the top your phone screen. You have to flash the boot.img for the specific rom you are trying to install. See the rom thread for the correct method.
Check your radio and Hboot version in bootloader. If you have the newer radio (xxx.xxx.928) and Hboot (1.57), you are limited on the roms that will actually work. Check the CDMA development thread for roms that specify OTA compatible.
Good luck. If you have any more questions, feel free to ask.

pedantfool said:
DISCLAIMER: I'm completely lost, so please break things down into bite-size steps or at least expect some follow-up questions on my part. I'm one of those desperate guys who is attempting to just have a working phone tomorrow. Any help will get as many presses of the thank button as I can possible give.
After several hours of plodding and poking and searching I've managed to do some possibly irreparable damage to my htc one v. Whenever I try to boot the phone it starts up with the htc developer red text "development use only" etc etc. I can access the bootloader and recovery thankfully, so I guess there's hope.
I think the source of my troubles is what's addressed by the essential reading at the top of this sub-forum, ie distinguishing between GSM and CDMA. I think (and this is an assumption here) that despite being in the USA on virgin, the fact that I can shove a sd-card in there means it's GSM (correct me if I'm wrong. please). EDIT: It seems that the phone only works with the CDMA version of TWRP, so I guess that might be an indicator.
Info: htc one v, virgin USA, using TWRP 2.3.3.0, attempted to flash Rom using various versions of Paranoid Android
What I've done thus far:
1. Unlocked bootloader
2. Flashed recovery
2.5. Created backup
3. rooted device (I downloaded rootchecker or somesuch app and was able to confirm that I had rooted my device)
4. Wiped cache and dalvik cache (I think that's what it's called).
5. Attempted to do a factory reset (failed).
6. Attempted to flash ROM (failed)
7. Restarted Device (got stuck on dev screen for the first time).
8. Tried recovering using backup created earlier (which just booted me into the dev screen of doom again).
9. Tried partitioning sd card in an attempt to perform a factory reset (wiped everything including backup).
10. Factory Reset failed with a message about not being able to mount /sd-ext.
11. Tried flashing rom again with different version of PA for shiggles (it worked! oh frabjous day!)
12. Rebooted phone only to get stuck on the dev screen again.
Guides I've used/perused/glanced at:
1. http://forum.xda-developers.com/showthread.php?t=2154635
2. http://forum.xda-developers.com/showthread.php?t=1598964
3. http://www.idroidspace.com/jelly-bean-4-2-2-paranoid-android-custom-rom-for-htc-one-v/
4. http://techmell.net/android-tips/ho...paranoid-android-4-1-2-jelly-bean-custom-rom/
5. http://androidlegend.com/upgrade-ht...ing_wp_cron=1369722527.0674550533294677734375
6. http://www.youtube.com/watch?v=a3pof_WSEEI
I've been at this for nigh on 7 hours and all I have to show for it is a phone I can't use. Help.
Click to expand...
Click to collapse
Which ROM you have flashed?
Did you install boot.IMG according to your ROM?
Sent from my HTC T320e

If you're restoring "stock" sense 4.0 ROM, you need to flash a kernel that will work with it. Try Titanium-KISS or Stock. The stock one should have been kernel should have been backed up, it's labeled boot.IMG in the backup folder. EDIT: Since you are CDMA, you need to flash this kernel in Fastboot to get it to boot: http://forum.xda-developers.com/showthread.php?t=2024758. Be sure you flashed the CDMA ParanoidAndroid as well, and not the GSM one.

followup
FIRST: Just thought of something that might be very important, I only had a version of android 4.0 installed on my phone. Will that make a difference when installing roms intended for later versions of android? If so, I feel like a huge knuckle-dragging fool.
Update: Was able to install and boot using PACman, but ran into a boot-loop.
But to follow up to your questions:
MameTozhio said:
If you're restoring "stock" sense 4.0 ROM, you need to flash a kernel that will work with it. Try Titanium-KISS or Stock. The stock one should have been kernel should have been backed up, it's labeled boot.IMG in the backup folder. EDIT: Since you are CDMA, you need to flash this kernel in Fastboot to get it to boot: http://forum.xda-developers.com/showthread.php?t=2024758. Be sure you flashed the CDMA ParanoidAndroid as well, and not the GSM one.
Click to expand...
Click to collapse
I'll admit I've had a hard time find a definitive version of PA or really any other Rom. I've tried going through their thread here and downloading one of the "stables" (http://goo.im/devs/gannon5197/paranoid/primoc/stables/). I've also used other unofficial versions of PA (http://forum.xda-developers.com/showthread.php?t=1799372). I'm currently downloading PACman to see if that will make any difference.
[email protected]@ said:
Which ROM you have flashed?
Did you install boot.IMG according to your ROM?
Sent from my HTC T320e
Click to expand...
Click to collapse
I did flash my boot.img using the method explained here:
Copy the kernel image (boot.img file you have extracted from zip file of ROM) to folder in which you have kept your fastboot files.
In the same folder, right click while holding shift button and select ‘Open command window here’.
A command window will appear on your screen. In command window type ‘fastboot flash boot boot.img’ and press enter.
On your screen you will get message ’OKAY/Finished’. You have successfully flashed kernel. Now you can disconnect your phone from computer.
http://androidlegend.com/upgrade-ht...ing_wp_cron=1369722527.0674550533294677734375
riggerman0421 said:
#5 The failed warning is due to lack of a SD EXT partition on your sd card. If you didn't re-partition it, you will get that failed warning. No big deal as it is wiping everything else correctly.
Click to expand...
Click to collapse
I'd like to think I'd partitioned it properly, but I keep getting a "unable to mount sd-ext" or "unable to wipe sd-ext" message when I attempt a factory reset. I've tried formatting the the mini sd and set the file type to FAT32, but to no avail as the errors persist. I know you said not to be too concerned, but I keep failing the system wipe from your next suggestion because of that error.
#6 You also need to wipe system prior to flashing your new rom.
After flash your new rom, you will need to connect to your pc and boot into bootloader. Make sure it says "Fastboot USB" at the top your phone screen. You have to flash the boot.img for the specific rom you are trying to install. See the rom thread for the correct method.
Click to expand...
Click to collapse
Now how important is it that I flash the boot.img after I have flashed the rom? I've been doing it beforehand, but does doing it afterward make a difference?
Check your radio and Hboot version in bootloader. If you have the newer radio (xxx.xxx.928) and Hboot (1.57), you are limited on the roms that will actually work. Check the CDMA development thread for roms that specify OTA compatible.
Click to expand...
Click to collapse
Those both match my radio and bootloader, what does that imply? I'm planning on flashing this rom: http://forum.xda-developers.com/showthread.php?t=1948034
Will that work?

No, it won't. You have the newer updated hboot and radio. That is the source of your boot loops. The only compatible roms at this time are MyOneV, ExtremeSemse, and RhythmicRom. You can also use Cyanprimo, but you'll have flash the boot.img from RhythmicRom.

Now I've downloaded RythmicRom and I'm still stuck in a boot loop. I'm sorry for being a bit thick, but could you link some roms that would be compatible or explain what I need to be looking for?
Version I downloaded: http://forum.xda-developers.com/showthread.php?t=2147407

You'll need to download the 1.2 update, then extract the boot.img from that. The boot.img in the Rom doesn't work with the new update.

So I've been reading up on the issue over here: http://forum.xda-developers.com/showthread.php?t=2018518&page=14
and while I don't claim to understand it all, I believe I get the gist of it.
I also've managed to get RythmicRom working thanks to riggerman. I guess I'll just play the waiting game until someone rolls out a fix or just replace my phone (though that's very much in the long-run).
Once again, thanks to everyone and hopefully this will be the last we see of this mess.

Glad you got it running, and glad I could help.

[Q] [ROM][10 Sep][4.0.4][Sense 4.1 Lite][OTA|HUB|EQS... -- stuck bootscreen

Greetings,
I would have liked to post this questions, where it belongs to, but I'm new to this forum, so I put it here.
Last September I've updated my DHD following the instructions given in the thread mentioned in the headline and everything was fine. Yesterday in the evening, I got the notification to restart using the recovery mode, because something in the context of the superuser should be updated or modified. Because it was not the first time, I just did it. But this time, after rebooting, the device stopped with the HTC bootscreen (green HTC on white background).
After 10 minutes I took out the battery and restarted again. Again I was able to choose recovery mode, but while starting the DHD got stuck with the bootscreen. I decided to wait and just put it aside showing the boot screen, but the result this morning was that the battery is empty and nothing changed.
Does someone know about that issue and what do I need to do to get the device to work again? Why was this update needed in the first place?
Thanks a lot in advance...

im not sure why
but have you tried re-flashing the ROM?

PHOENIX-9 said:
im not sure why
but have you tried re-flashing the ROM?
Click to expand...
Click to collapse
Not yet. I was afraid to loose all data and maybe exchaning a file would also do the job. I mean, the update of the superuser component has changed something and this could be corrected again.

If you don't wipe your data partition (dirty flash) and you flash the exact same ROM, you shouldn't lose data.

KKrittel said:
Not yet. I was afraid to loose all data and maybe exchaning a file would also do the job. I mean, the update of the superuser component has changed something and this could be corrected again.
Click to expand...
Click to collapse
try to back up your ROM
do a clean install..then restore only the data (advanced restore)..wipe dalvik and cashe
if it didnt boot..you can restore your data using titanium backup pro from the CWM back up

PHOENIX-9 said:
try to back up your ROM
do a clean install..then restore only the data (advanced restore)..wipe dalvik and cashe
if it didnt boot..you can restore your data using titanium backup pro from the CWM back up
Click to expand...
Click to collapse
Tried to make a backup, but it recovering did not work. Doesn't matter. I just flashed the same image again, downloaded 'my' apps and restored the status from before the crash.
Nevertheless the same notification showed up, saying that the superuser kernel needs to be updated and I should use 'recovery mode' again. With a bad feeling, I did it again, but this time it works.
So to sum it up: device was useless for some days, restored it with some effort and now it works again. But I need to get prepared for the next time and to think of an app to backup all apps including app-data.
...but as always, this is a task for laaaaater
Thx,
Karl

Edit Oct 17, 2014 - Encrypt your device/phone with custom ROM

Disclaimer: I am not responsible for any damage or liability arising out of these steps. I did not invent anything, I just tried something. Only move forward at your risk
If you don't agree ... stop reading and move on...
Background: Our phone has access to so much personal information that its scary if it fell into wrong hands. The only way to fix this is to encrypt phone. I did lot of research and here is a working solution that works for me - try at your risk.
Download Links:
a) Tested with ROM Stock 4.4.4 NH7 Galaxy S4 M919/Jfltetmo by @ShinySide
b) Tested with ROM |ROM|★KANGAKAT★|►KTU84P◄|4.4.4|Xposed|►8◄|6.26.14 by @iB4STiD
c) stock recovery AT&T S4 works with M919
d) Philz/CWM custom recovery
Encrypting with custom rom
1) Assume you are on custom recovery. - Backup everything first. Create a nandroid backup
2) Do a full wipe and install one of the two roms linked above (I have tested with few other roms ... none worked). Start the phone and set it up the way you want. Install all apps etc.
3) ODIN Stock recovery. See #c under download above. Its AT&T stock recovery but works for me. You need to know how to ODIN - find out. Doing this wrong will permanently damage your phone
4) Start your phone and turn on encryption. You will need to set lock type = password and will need to connect to charger and have 80% charge.
- Phone will do blank and stay blank for 20-30 minutes. Do not do anything. Encryption is happening behind the scenes.
- You might have to do this twice or thrice if it did not encrypt first time. For me the phone went blank first time and after 25 minutes it restarted but device was not encrypted. I redid the same steps and worked second time.
- If you interrupt the encryption process (battery pull or power up) you will see error message (encryption failed, reset device)
5) If all goes well you now have a password protected encrypted phone with custom rom!!! Check in Settings -> Security
6) You may install custom recovery ... but I don't see the point because you will need stock recovery to decrypt
To install another ROM
1) Reboot into stock recovery, then wipe data and cache (this removes encryption).
2) install your recovery of choice and install ROM using recovery. Philz/CWM
Credit goes to @Tronicus and his reply Flash a Rom on an Encrypted Android
Tronicus said:
How to Flash a rom on an encrypted Android phone (specifically this one, the I9505 SGH-I337).
The Problem: Once encrypted, you can't decrypt it easily. When encrypting the phone android will tell you you can only decrypt it using a factory reset. Naturally you assume it's talking about the "Factory Data Reset" option found in Settings --> Backup and Reset. But noooo, Android is lying through its ****ing teeth. Then you'll assume you have to wipe everything from your custom recovery mod (CWM, TWRP, or one of those). Wrong again! You'll get beautiful "can't mount /data" messages and more bull****. I read about a workaround that required installing the new rom using ADB, but I had ingeniously disabled USB debugging prior to wiping everything, so I only got so far with that option (plus it's tediously long if you haven't installed all the necessary software already and don't feel like bricking your phone because you made a typo in the command line). So, apparently the only other way to really format that partition free of its encryption is to use a stock recovery. So:
Short Version for Godlike users who know automatically how to do all this **** without any help (mimicking how most help posts are finely detailed on this site): Flash stock recovery, wipe everything, flash your custom recovery and install your new rom.
Long version for us mortals who don't know everything and haven't already downloaded already every single bit of software on earth:
Backup all the stuff you want to save. This process will truly wipe EVERYTHING. You can do it manually, or you can use an app like Titanium Backup Pro to help you (find it on Google Play Store). Here's a nice guide which recommends what to restore and what not to restore: http://forum.xda-developers.com/showthread.php?t=1480343
Flash the stock recovery using Odin. You can download a stock recovery from here: http://forum.xda-developers.com/showpost.php?p=49687791&postcount=3 It's the link called "I337MK2stockrecovery.tar.md5" In case you don't know how to flash it with Odin, this short guide will help: http://forum.xda-developers.com/showthread.php?t=1506697
In step 6 replace "recovery.tar.md5" with the stock recovery you downloaded.
Wipe everything from the Stock recovery console. This little ****er will **** up the encryption all those sissies couldn't touch. You're welcome. You boot into recovery mode from a turned off phone by pressing simultaneously the volume up key + the home key + the power key until you see blue text appearing in the top left corner of your screen.
Reinstall your custom recovery. In my case I had installed the rom BEFORE flashing in the stock recovery (apparently it works, you just can't boot because of the encryption), so I was able to boot into the new rom before I returned to my custom recovery. Weird. Anyways, I recommend CWM. You can pick it up from this link: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/jflte
For some weird reason they call the I337 version the "jflte" version. It's bonkers. Click there, and download the latest version that ends with .tar.md5. This version is upgradable via Odin, which we already used. Use the same instructions used as when you upgraded the stock recovery rom.
Boot into your recovery mod and flash your rom like you usually do.
A word about TWRP: it cost me many hours of work and I don't recommend it. Its website is outdated, and recommends using GooManager (which is no longer mantained) and doesn't work anymore for this. GooManager suggests using a new, different app, which doesn't have the option of installing TWRP. Then I tried using their TWRP Manager app from play store and the image file wouldn't download. Then I tried manually selecting the image file in TWRP manager that I downloaded from their site for use via the ADB method, and it bricked my phone... twice (using two different methods the app sugested). I tried so much because in theory TWRP has the ability to decrypt android's 4.4 encryption, but after looking at their github site I noticed it was filled with people's reports (including people with the S4) on how it wouldn't work decrypting squat. So I gave up, and installed CWM in 30 seconds.
Click to expand...
Click to collapse
Disclaimer: I am not responsible for any damage or liability arising out of these steps. I did not invent anything, I just tried something. Only move forward at your risk

cnewsgrp said:
One of the things I needed was the ability to encrypt my phone (device only not external SD) for security purpose. Our phones today gives access to lot of information that I would rather not fall in wrong hands. I did lot of research and here is a working solution.
Credit goes to @Tronicus and his reply Flash a Rom on an Encrypted Android
The quote looks long however it is really very simple. To install another ROM
- Install and reboot into stock recovery, then wipe data and cache (this removes encryption).
- Then install your recovery of choice and install ROM using recovery. Philz/CWM
This has been tested working on |ROM|★KANGAKAT★|►KTU84P◄|4.4.4|Xposed|►8◄|6.26.14 by @iB4STiD
This did NOT work on a Touchwiz ROM by same developer
I have not tested any other ROM
Click to expand...
Click to collapse
I don't know if it matters too much or not, but the stock recovery you linked to is for the AT&T S4. A good rule of thumb is to never use Odin to flash anything not specifically for your particular device... In this case the M919.
Sent from my SGH-M919 using XDA Premium 4 mobile app

lordcheeto03 said:
I don't know if it matters too much or not, but the stock recovery you linked to is for the AT&T S4. A good rule of thumb is to never use Odin to flash anything not specifically for your particular device... In this case the M919.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have tested stock recovery on M919 .. it works

Honestly im surprised its not talked about more since there is a big push for personal privacy when it comes to data. Encryption really is a pain in the ass to work with on android. Figuring out how to switch or update custom roms while encrypted will drive you insane. The easiest way is to just odin back to stock and start over, but that requires a computer anytime you need to flash anything.
I recently was trying out one of the 4.4.4 GPE roms and turned on encryption. It worked great until i started missing touchwiz and wanted to go back to HyperDrive TW. So the journey began...
First of all, i backed up everything to external storage since i knew everything on the internal storage would have to be wiped. I loaded the phone into recovery mode (using TWRP) and tried wiping, but all i got was a bunch of "Failed to mount" errors. Fine. Got the same error when trying to factory reset or wiping /system, /data, /cache, and anything else. Tried formatting to different file systems and then formatting back to the original but no luck. Fixing permissions didnt help. I just kept trying everything available multiple times.
Eventually it started wiping everything except the /data mount. Well... At least i could install new custom roms. Im not sure exactly what did it because i was just throwing everything at it. Anyways I got it to install, and booted into it. Nope.
Now it was saying I needed the password to decrypt the internal storage. It would detect wrong passwords fine, but as soon as i put the correct password in, it would allow me in, show the green android encryption picture, then blank screen. I thought it was just decrypting and setting up my rom but after a few hours my screen was still black and nothing was happening. Pulled battery and went back to TWRP.
I started wiping everything again and again and tried doing everything i could to wipe everything on the internal storage. Again, not sure what did it, but eventually got it all cleaned up and got a new rom installed and could boot into it.
The whole process probably took about 6-7 hours...
I dont even want to enable encryption on the new rom...

p-hil said:
Honestly im surprised its not talked about more since there is a big push for personal privacy when it comes to data. Encryption really is a pain in the ass to work with on android. Figuring out how to switch or update custom roms while encrypted will drive you insane. The easiest way is to just odin back to stock and start over, but that requires a computer anytime you need to flash anything.
I recently was trying out one of the 4.4.4 GPE roms and turned on encryption. It worked great until i started missing touchwiz and wanted to go back to HyperDrive TW. So the journey began...
First of all, i backed up everything to external storage since i knew everything on the internal storage would have to be wiped. I loaded the phone into recovery mode (using TWRP) and tried wiping, but all i got was a bunch of "Failed to mount" errors. Fine. Got the same error when trying to factory reset or wiping /system, /data, /cache, and anything else. Tried formatting to different file systems and then formatting back to the original but no luck. Fixing permissions didnt help. I just kept trying everything available multiple times.
Eventually it started wiping everything except the /data mount. Well... At least i could install new custom roms. Im not sure exactly what did it because i was just throwing everything at it. Anyways I got it to install, and booted into it. Nope.
Now it was saying I needed the password to decrypt the internal storage. It would detect wrong passwords fine, but as soon as i put the correct password in, it would allow me in, show the green android encryption picture, then blank screen. I thought it was just decrypting and setting up my rom but after a few hours my screen was still black and nothing was happening. Pulled battery and went back to TWRP.
I started wiping everything again and again and tried doing everything i could to wipe everything on the internal storage. Again, not sure what did it, but eventually got it all cleaned up and got a new rom installed and could boot into it.
The whole process probably took about 6-7 hours...
I dont even want to enable encryption on the new rom...
Click to expand...
Click to collapse
Yeah Encryption does not seem to work on TWZ roms. I tried on G Eye without luck.

I have updated op. Please check

Encryption will slow down your phone quite a bit. More battery usage + more CPU usage + slower phone = not worth it unless you've got some very private stuff you don't want being shared. Otherwise, 3rd party apps that lock a lot of files, can encrypt certain files, and hide others will do the trick perfectly well.'
Not trying to bash fully encrypting your phone, but I've tried it before and although I am very pro privacy, I had to eventually take it off due to all the extra hassle it created.

Don't know about slowing down. I am not seeing it. I feel differently about security.

[Q] "System UI has stopped" forever after installing custom ROM.

I'm not very good at Android technical stuffs as I'm new to it but learned decent basic knowledge before doing any rooting and flashing stuffs.
To start off, I installed ARHD 22.1 back in December and then upgraded to ARHD 30.1 just yesterday, successfully. I'm S-On, using Taiwan HTC One M8x 2.5 ghz unlocked.
I then decided to add the eXtremeBeats audio mod which is compatible to Android L. I followed the instruction there ( DL File, put to phone, flash via recovery, wipe cache & dalvik, reboot ). At the reboot the problem starts, after optimizing the apps, and then it says "starting apps" there it got stuck, I waited it for an hour and a half and decided to force shut my phone. So after turning it on again, it's now stuck on the HTC logo only. I decided to re-install ARHD 30.1 at that same day, successfully installed but when the phone starts, it says "Unfortunately, HTC Dot View has stopped" then followed by "Unfortunately, System UI has stopped". So yeah, I don't have any on screen bottons on my phone, no slide down notification, but can access apps ( no going back though ). I tried to wipe cache & dalvik again, tried re-installing the ARHD 30.1 again for the 3rd time, no luck.
I searched my problem at Google but mine's different. Their "Unfortunately, System UI has stopped" is like soldemly happening in the middle of phone usage and returning back to normal after some seconds, mine gets that problem at the very start up and the UI doesn't return.
What did I do wrong? What must I do? Thanks in advance!
Edit: I noticed that my OS is missing where it's supposed to say something like 3.28.xxx.x. I wiped everything including system at the time I install ARHD 30.1 the second time (where the problem occurred). I think this might have caused the problem? How do I fix this?

Restore your nandroid and see what happens.

redpoint73 said:
Restore your nandroid and see what happens.
Click to expand...
Click to collapse
Yes, I'm currently trying to figure out on how to do this. I'm having problems.
I have a Nandroid backup file in my PC. But I don't know how to push it to /sdcard/TWRP/BACKUP/. I tried the pushing file tutorial via mini-sdk and some cmd commands from ARHD's website tutorial, it can push to /data but I can't get it to work on /sdcard ( I tried to >mount /sdcard == gives error ). The other way I know is to transfer the Nandroid backup file from PC to phone normally via the file copy pasting, my computer can recognize my phone having the ARHD 30.1 (w/ UI problem) installed and USB Debugging on, though I can't access the storage or transfer files.
How do I push my Nandroid backup file from PC to /sdcard/TWRP/BACKUP ... ? Any advice please? I think this will solve my issue.

TheMabaet said:
How do I push my Nandroid backup file from PC to /sdcard/TWRP/BACKUP ... ? Any advice please? I think this will solve my issue.
Click to expand...
Click to collapse
Yes, the syntax for adb pushing a TWRP backup to internal storage can be challenging. If you have a removable SD available, that might be easier, change the save location in TWRP to that. Then make a "mock" backup, purely so that the TWRP folder is created on the SD card. Then either copy/paste your nandroid to the SD with your phone connected to your PC; or use a card reader connected to your PC.
Alternately, you can try to mount the internal storage in TWRP instead of in the OS. That might work better.

redpoint73 said:
Yes, the syntax for adb pushing a TWRP backup to internal storage can be challenging. If you have a removable SD available, that might be easier, change the save location in TWRP to that. Then make a "mock" backup, purely so that the TWRP folder is created on the SD card. Then either copy/paste your nandroid to the SD with your phone connected to your PC; or use a card reader connected to your PC.
Alternately, you can try to mount the internal storage in TWRP instead of in the OS. That might work better.
Click to expand...
Click to collapse
Amazing! I understand the first method, but the alternative... can you explain a bit further? As I tap the Mount button at the main page of TWRP, it says "Select Partitions to Mount:", having System, Cache, Data, Micro SDCard, USB-OTG as options. And then nothing else to do, I see no any other button. Clearly I didn't understood the practice, and I google "How to mount internal storage to TWRP" but somehow didn't get any good result. Could you please tell me how it is done or link me to a guide?
Edit: The first method is fine, though I'd like to know how the second one is done. I apologize if you find me cumbersome but I'd like to learn, might come in handy at some peculiar point. I'm curious as what you said that that might work better but I can't perform the latter, it got me really cheesy
EDIT 2: I managed to do the BACKUP. But now it got stuck to BOOT LOOP. I tried to wipe data, cache, and dalvik... but still it BOOT LOOP. What now?

I'm having a similar problem, did you manage to fix it? How? Thanks.

NOT flashing the correct firmware / Kernel is a most frequent cause of SystemUI crashes. Flash the correct firmware/Kernel to correct this.

wth is wrong with my backup?
alright is there a specific solution to this? me and my mother both have the same phone so i took the lollipop backup from her, renamed it like mines and restored it. once i finish the restore and boot up im greeted with ''unfortunately system ui has stopped''. what gets me crazy and confused is that it works perfectly sometimes when i erase the system and everything then when i restore the same lollipop backup and here we go again, system ui has freakin' stopped! this doesnt happen to any other kitkat backup only lollipop.
i have twrp recovery 2.8.02
my hboot is 2.49
i am currently having s on.
i am sick of htc and their stupid s off and on thing like why should we pay 25 dollars i mean android hacking should be open source right? convert 25 $ to riyals and i cold live for a week, happily!!!

kimosab said:
alright is there a specific solution to this? me and my mother both have the same phone so i took the lollipop backup from her, renamed it like mines and restored it. once i finish the restore and boot up im greeted with ''unfortunately system ui has stopped''. what gets me crazy and confused is that it works perfectly sometimes when i erase the system and everything then when i restore the same lollipop backup and here we go again, system ui has freakin' stopped! this doesnt happen to any other kitkat backup only lollipop.
i have twrp recovery 2.8.02
my hboot is 2.49
i am currently having s on.
i am sick of htc and their stupid s off and on thing like why should we pay 25 dollars i mean android hacking should be open source right? convert 25 $ to riyals and i cold live for a week, happily!!!
Click to expand...
Click to collapse
Hboot should be 3.19 in Lollipop. 2.49 is Android4.4.2 KitKat
Also, update your recovery. 2.8.7.0 works wonderfully.
Bottom line is you need to update your firmware before you try to restore a Lollipop backup.
---------- Post added at 06:40 PM ---------- Previous post was at 06:36 PM ----------
Get into ADB/fastboot and do fastboot getvar all
Post the readout here minus your IMEI and serial# (that's private information you should never post on a public forum)
With that information, it will help us to direct you on the proper way to update, and to provide you with the proper downloads for your device.

kimosab said:
i am sick of htc and their stupid s off and on thing like why should we pay 25 dollars i mean android hacking should be open source right? convert 25 $ to riyals and i cold live for a week, happily!!!
Click to expand...
Click to collapse
Why bash on HTC and sunshine s-off ? You unlocked it, flashed twrp.....that's something HTC didn't nor the guys from sunshine. And you don't need s-off, it's not mandatory but it can make it easier.
I would kindly suggest to drop the ignorant attitude towards the wrong people and focus on the problem you have to solve.

kimosab said:
alright is there a specific solution to this? me and my mother both have the same phone so i took the lollipop backup from her, renamed it like mines and restored it. once i finish the restore and boot up im greeted with ''unfortunately system ui has stopped''.
my hboot is 2.49
Click to expand...
Click to collapse
That is not a valid hboot number for the M8 (which this forum section is specific to). I think you have a One Max.
But as mentioned, you can't just migrate a nandroid from one phone to another. The firmware needs to match also. Running a LP nandroid with KK firmware is going to result in issues.
---------- Post added at 12:00 PM ---------- Previous post was at 11:59 AM ----------
xunholyx said:
Hboot should be 3.19 in Lollipop. 2.49 is Android4.4.2 KitKat
Click to expand...
Click to collapse
Corresponding hboot for Android 4.4.2 on this device is 3.16.
---------- Post added at 12:02 PM ---------- Previous post was at 12:00 PM ----------
Mr Hofs said:
Why bash on HTC and sunshine s-off ? You unlocked it, flashed twrp.....that's something HTC didn't nor the guys from sunshine. And you don't need s-off, it's not mandatory but it can make it easier.
I would kindly suggest to drop the ignorant attitude towards the wrong people and focus on the problem you have to solve.
Click to expand...
Click to collapse
Agreed. S-off isn't the problem, and not needed to remedy the previous user's issue. Main problem is lack of research before messing with the phone.

found an awesome solution. i used to have a nandroid of android 4.4.3, so i restored it, didn't do any kind of wipe and then restored my moms nandroid backup of android L. its working great! i have the htc one m7 dual sim m7_cdug 802w

--delete

Boot loop at the final stap in rooting/unlocking bootloader

I have followed the instructions from Max at galaxynote4root http://galaxynote4root.com/galaxy-note-4-root/how-to-root-unlock-bootloader-on-galaxy-note-4/5/. I got all the way through to the final step which is go into TWRP recovery, install the Oscar kernel and SuperSU zip files. I did not extract these files. Once I did that I got into a boot loop. I get by the Verizon logo to the UI and then it starts rebooting. Since there is not much discussion activity at Max's site, I thought if anyone here could help me.
After the UI comes up and before it goes in the boot loop, I get messages saying "Unfortunately xxxx has stopped." It varies about sometimes it is Knox. S Pen, Google Play, etc.

Try a factory reset by going into recovery and wiping delvik, cache, and data

MonstaSaleens said:
Try a factory reset by going into recovery and wiping delvik, cache, and data
Click to expand...
Click to collapse
That improved the situation. It is no longer in a constant boot loop, but it will still reboot when I manually start it or reboot it. When it starts it says "unfortunately KNOX has stopped running." It was doing that before, too.
I have confirmed I have root and and unlocked bootloader.

Redownload the rom.
Wipe data, cache, dalvic cache and system.
Install rom
Then kernel
And supersu.
Reboot and you should be fine
---------- Post added at 06:32 AM ---------- Previous post was at 06:30 AM ----------
If it continues I'd get a Odin flushable and use the pit file for repatriationing of the system. Maybe something went wrong..... Idk

Just a quick question: Did you use a micro SD card as part of the process? Did you remove this card after you were done unlocking the bootloader?
I know the process has you reformat the card, but I am asking if you have tried booting with the card removed.

codydixon said:
Redownload the rom.
Wipe data, cache, dalvic cache and system.
Install rom
Then kernel
And supersu.
Reboot and you should be fine
---------- Post added at 06:32 AM ---------- Previous post was at 06:30 AM ----------
If it continues I'd get a Odin flushable and use the pit file for repatriationing of the system. Maybe something went wrong..... Idk
Click to expand...
Click to collapse
Just followed your instructions. Everything was fine until I installed the kernel and supersu. I hate to be stuck when I'm so close.

ssj4gogeta2003 said:
Just a quick question: Did you use a micro SD card as part of the process? Did you remove this card after you were done unlocking the bootloader?
I know the process has you reformat the card, but I am asking if you have tried booting with the card removed.[/QUOTE
OK, tried that, and it worked--once. When I reboot with the SD card out, it either won't start or goes back into a boot loop.
Click to expand...
Click to collapse

Although it didn't seem very warm to me, I pulled the battery and let it sit for an hour. When I started it back up, everything was fine.
However, how do I re-enable the use of the SD card. I am afraid if I put in back in, I'll go back into the boot loop?

MrNetwork said:
Although it didn't seem very warm to me, I pulled the battery and let it sit for an hour. When I started it back up, everything was fine.
However, how do I re-enable the use of the SD card. I am afraid if I put in back in, I'll go back into the boot loop?
Click to expand...
Click to collapse
You'll need to connect the micro sd card itself to the computer and format it there. I have used Rufus (https://rufus.akeo.ie/) in the past to do this, but you may use any formatting program that you are familiar with. I recommend FAT32 as your format unless you move files over 4 GB to and from the card.

Thanks. I've rebooted it a couple of times after doing this, and it still is working! Now, should I install a 6.0 ROM or leave well enough alone?

MrNetwork said:
Thanks. I've rebooted it a couple of times after doing this, and it still is working! Now, should I install a 6.0 ROM or leave well enough alone?
Click to expand...
Click to collapse
It will depend on what version of firmware you are currently running. Most 6.0 ROMs require that you are using N910VVRU2CPD1 or N910VVRU2CPF3 for proper use. Please go into About Phone in Settings and check the Baseband Version field to make sure that you have one of those two in there. Flashing a 6.0 ROM with 5.1.1 firmware will cause issues with mobile signal and can make it impossible to use wifi.
If you find that you are running 5.1.1 firmware, then you have two choices: Flash a 5.1.1 ROM and call it a day or go through the process of unlocking the bootloader for 6.0.1 firmware. It's important to note that this will be a different process than the one you just went through. Be sure to research it thoroughly before attempting it. Hsbadr is a great developer and I believe he has a process for that, but it's been a while since I did it myself.

Back in a boot loop again. Once I've loaded the system image, I can reboot several times and everything is stable. As soon as I obtain root by installing the Oscar kernel and BetaSU, the phone becomes unstable. It might boot properly at first, but I still get "XXX has failed to start" where XXX can be any of a number of apps. If I let that go on without first shutting it down, it will go into a boot loop. However, if I do shut it down and restart it will also eventually go into a boot loop. Obviously this phone can't be my daily driver until I get it stable.
Before I install the rom each time, I wipe data, cache, dalvic cache and system.
I wonder if the kernel is the issue?

MrNetwork said:
Back in a boot loop again. Once I've loaded the system image, I can reboot several times and everything is stable. As soon as I obtain root by installing the Oscar kernel and BetaSU, the phone becomes unstable. It might boot properly at first, but I still get "XXX has failed to start" where XXX can be any of a number of apps. If I let that go on without first shutting it down, it will go into a boot loop. However, if I do shut it down and restart it will also eventually go into a boot loop. Obviously this phone can't be my daily driver until I get it stable.
Before I install the rom each time, I wipe data, cache, dalvic cache and system.
I wonder if the kernel is the issue?
Click to expand...
Click to collapse
I need more information to help you out. Please answer the following:
What baseband is your phone at right now? (Refer to my post above for where to find it.)
What ROM have you installed? (Be sure to include Android version as well as name)
Oscar Kernel is specifically for use with 6.0.1 Touchwiz ROMs. If you aren't on 6.0.1 and you haven't installed a Touchwiz-based ROM, then there will be issues.

ssj4gogeta2003 said:
I need more information to help you out. Please answer the following:
What baseband is your phone at right now? (Refer to my post above for where to find it.)
What ROM have you installed? (Be sure to include Android version as well as name)
Oscar Kernel is specifically for use with 6.0.1 Touchwiz ROMs. If you aren't on 6.0.1 and you haven't installed a Touchwiz-based ROM, then there will be issues.
Click to expand...
Click to collapse
Thank you. I finally figured it out. The problem was with oscar_kernel_v0.2. Instead I am using Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P. I'm going to stay with 5.1.1. The only trouble I am having now is with My Tracks not showing the map. I know it's been deprecated by Google, but it still is working on my LG G4. However, I'm not trying to hijack this thread. I'll start a new thread for this issue.
This is now the fastest phone I've used after deleting bloatware and running Nova Launcher.

Good to hear. Enjoy the phone.