Related
I've spent about 3 days and worked closely with a few knowledgeable people outside of this forum. I'm desperate and a bit terrified to start this topic. I've read too many to know how frustrating it to answer the same questions over and over again.
In short:
a.) Was running CM9, flashed using CWM. (Did not have issues and have flashed in the past with other roms successfully)
b.) Went to flash another ROM (can't remember which one) and did not back up (big mistake, troll away)
c.) Cannot get phone to start, can flash roms all day long and only get to their boot/splash screens. It will sit there until my battery dies
d.) I've tried Galaxy Nexus Toolkit and Wugs
e.) I've installed TWRP and formatted drive
f.) I've read and followed 3 full days of different forums and still can't figure this out. I've tried so many things it would take forever to type.
I'm severely desperate.
Will someone help me start from scratch and walk me through a surefire process. At this point, I'm lost. Nothing seems to work.
Apologies in advance and I am willing to accept the bad vibe. I'm lost.
Phone is a Verizon Galaxy Nexus
Did you try fully wiping, formatting /system, flashing a ROM and wiping cache after that? Or flashing another kernel?
Wow finally something
Wow! I finally got something to load. I'm on 4.0.2. I need to get back to jelly bean.
Wow, I'm stuck in nearly the same rut as you are in right now.
Experienced flasher here too - I was using the Xylon v18 until now, and Paranoid Android 2.99 before this. Yesterday night my phone rebooted after some weird Contacts application opening issue. And kept rebooting. One backup restore said there was an I/O error in /data/data/com.android.contacts or something. The backup never booted.
I have TWRP 2.4.0.0.
I tried new ROMs, different ROM backups, a few kernels, formatting /data including internal memory, tried Adb sideloading (said Read Only file system), finally installed Xylon v18 through Usb-otg, but it refused to go beyond Google logo. Restored a backup through OTG, and the same continues.
Could someone tell me what could be going on here?
I swear I was about to put in a post similar to the OP.
Thanks for the headsup just_some_dude, I'll go try an ICS rom now.
---------- Post added at 01:59 PM ---------- Previous post was at 01:23 PM ----------
Edit1 : So it looks like my phone wanted to remind me what it feels like to actually jump with joy!
Installed the deodexed version of stock rom, and after a failed first boot, "Android is upgrading".
Edit2: Scratch that, couldn't get through phone setup. Changed to CWM 6.0.2.3. Flashed radio and RIL, PA2.99 again, and for now it seems to be working.
desktopfusion said:
Wow, I'm stuck in nearly the same rut as you are in right now.
Thanks for the headsup just_some_dude, I'll go try an ICS rom now.
---------- Post added at 01:59 PM ---------- Previous post was at 01:23 PM ----------
Click to expand...
Click to collapse
I was able to IMM76K, but phone wants to push newer version. I can't upgrade newer version without it getting stuck on that splash screen for the rom. I'm putting IMM76K back on.
So, weird. So much of this is not making sense to me.
Rebooting continuing for me despite different kernel and cache/dalvik wipes.
I'm sorry, absolutely not trying to hijack this thread. Only writing symptoms incase anyone notices something they have gone through too.
Baah, this is going to properly spoil my weekend.
Why not try to go back to stock by flashing the stock images first? At least you'd know if the phone works...
Thank you for the input.
I did, but in the zip, deodexed form. For me, all things are now pointing to Wifi causing the reboots, even when the Stock 4.2.1 was used I couldn't go past phone setup.
On PA2.99, after switching wifi off as soon as it booted, the phone is now stable for 10 minutes for the first time in 8 hours of trial-and-error.
Shouldn't XXLH1 flashing have fixed such things?
FIXED! It was a corrupted /data partition, which showed the /data/media or /sdcard was already 11 gb full after a full wipe with TWRP.
A /data and /data/media format with CWM did the trick!
desktopfusion said:
Thank you for the input.
I did, but in the zip, deodexed form. For me, all things are now pointing to Wifi causing the reboots, even when the Stock 4.2.1 was used I couldn't go past phone setup.
On PA2.99, after switching wifi off as soon as it booted, the phone is now stable for 10 minutes for the first time in 8 hours of trial-and-error.
Shouldn't XXLH1 flashing have fixed such things?
Click to expand...
Click to collapse
For reference, that's not going back to stock. Back to stock means flashing the Google factory image, which would have also formatted your data partition, so do that in future
EddyOS said:
For reference, that's not going back to stock. Back to stock means flashing the Google factory image, which would have also formatted your data partition, so do that in future
Click to expand...
Click to collapse
Ah, I did not know flashing the image wiped data partition as well, thanks!
I stopped looking for the image when I couldn't find JOP40G on the site. Classic case of beggars trying to be choosers. :cyclops:
I just tried to flash mmuzzy and gapps using wugs and am sitting at the Jelly Bean 'X' splash screen. I set it up so wugs would wipe data cache and Dalvik. Don't know what it is, but I cannot get Jelly Bean on this phone.
Tried flashing the Stock factory image? Not through recovery, but through fastboot. That is what I did ultimately.
Actually, my problem was deeper. My /userdata partition had some errors. On going through some posts here on /data partition corruption issues, these links helped me a lot, and made the phone ultimately much smoother than it ever was!
Definitely try the e2fsck command through adb shell while in recovery with /data partition unmounted. Try this before you flash a stock ROM image.
Here you go. I think these should help you too:
1. http://forum.xda-developers.com/showthread.php?t=1541379&page=4
2. http://forum.xda-developers.com/showthread.php?t=2025675
3. http://linux.101hacks.com/unix/e2fsck/ - e2fsck command options if you need help.
If adb asks you to 'check forced' because it finds problems, just use
Code:
adb shell "e2fsck -f /dev/block/platform/omap/omap_hsmmc.0/by-name/userdata"
I'm guessing it was all a result of months of flashing huge amount of ROMs. :angel:
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
Hi all,
Happy new owner of European model HTC One M9. Now stuck with white HTC boot screen and problems to turn it off and random strange things... I'm lost and need help desperately...
Followed all guides in unlocking through htc-dev, installing TWRP 2.8.6.4 (beta).
Made a copy of Stock ROM through nandroid backup.
Flashed SuperSU (UPDATE-SuperSU-v2.46).
Advanced wipe (did I by any means delete internal system?)
When flashing Android_Revolution_HD-One_M9_4.1_eda061 everything went haywire. Got message at end stating that not all processes were finished. Something with regard to E:mount -0 bind '/data/media/'sdcard' process errored with error=255. Now lots of issues...
1) I couldn't get passed the white boot HTC One screen. Had to keep my finger on the power off for ages.
2) Bootloader shows software status: modifed. unlocked. s-on. I assume this is correct?
3) Going into recovery I get a strange HTC message: This build is for development purposes only (+ disclaimer not to distribute outside HTC bla bla bla). Is this normal?
4) when I try to restore my Stock ROM through fastboot I get to the setup of the device, but then FC of different programs. Back, home and settings button are non-responsive. Even entered a strange HTC error check. Upon rebooting, clearing cache and Dalvik, I am stuck at white boot screen. Now I can't even get into android OS setup anymore.
I have tried nr 4 above several times without success. I do get a strange "Invalid sparse file format at header magi
erasing 'system'..." is this normal? I get OK at end - but then still back to white boot screen.
Is my system totally buggered? What have I done wrong? I've flashed HTCs and Samsungs several years as an amateur but I feel like a total noob... Help? Anyone?
robned said:
Hi all,
Happy new owner of European model HTC One M9. Now stuck with white HTC boot screen and problems to turn it off and random strange things... I'm lost and need help desperately...
Followed all guides in unlocking through htc-dev, installing TWRP 2.8.6.4 (beta).
Made a copy of Stock ROM through nandroid backup.
Flashed SuperSU (UPDATE-SuperSU-v2.46).
Advanced wipe (did I by any means delete internal system?)
When flashing Android_Revolution_HD-One_M9_4.1_eda061 everything went haywire. Got message at end stating that not all processes were finished. Something with regard to E:mount -0 bind '/data/media/'sdcard' process errored with error=255. Now lots of issues...
1) I couldn't get passed the white boot HTC One screen. Had to keep my finger on the power off for ages.
2) Bootloader shows software status: modifed. unlocked. s-on. I assume this is correct?
3) Going into recovery I get a strange HTC message: This build is for development purposes only (+ disclaimer not to distribute outside HTC bla bla bla). Is this normal?
4) when I try to restore my Stock ROM through fastboot I get to the setup of the device, but then FC of different programs. Back, home and settings button are non-responsive. Even entered a strange HTC error check. Upon rebooting, clearing cache and Dalvik, I am stuck at white boot screen. Now I can't even get into android OS setup anymore.
I have tried nr 4 above several times without success. I do get a strange "Invalid sparse file format at header magi
erasing 'system'..." is this normal? I get OK at end - but then still back to white boot screen.
Is my system totally buggered? What have I done wrong? I've flashed HTCs and Samsungs several years as an amateur but I feel like a total noob... Help? Anyone?
Click to expand...
Click to collapse
the disclaimer is normal, and all that other stuff. before the fastboot restore did you flash stock recovery, I'm not sure but I think you have to, someone correct me if I'm wrong. pn advanced wipe you wipe cache-dalvic cache-system and data. nothing else before flashing a rom, if it has aroma installer select full wipe.
Aldo101t said:
the disclaimer is normal, and all that other stuff. before the fastboot restore did you flash stock recovery, I'm not sure but I think you have to, someone correct me if I'm wrong. pn advanced wipe you wipe cache-dalvic cache-system and data. nothing else before flashing a rom, if it has aroma installer select full wipe.
Click to expand...
Click to collapse
Hi,
Many thanks for your input. I tried to do a fastboot restore stock recovery (OTA 401.15) and afterwards a fastboot of my Stock ROM nandroid backup. It all seemed to work well (took longer than before - so I guess things got written to system) but I get foreclosures on several programs - most importantly Sense UI (even EasyAccessService and others less important as well). The SenseUI means I dont have any working buttons for apps, back and home. I wanted to see if I could delete the cache for SenseUI - but as soon as I try to go to apps, I get FC on App Helper. Same if I want to install anything.
- so I'm lost again... Any ideas?
robned said:
Hi,
Many thanks for your input. I tried to do a fastboot restore stock recovery (OTA 401.15) and afterwards a fastboot of my Stock ROM nandroid backup. It all seemed to work well (took longer than before - so I guess things got written to system) but I get foreclosures on several programs - most importantly Sense UI (even EasyAccessService and others less important as well). The SenseUI means I dont have any working buttons for apps, back and home. I wanted to see if I could delete the cache for SenseUI - but as soon as I try to go to apps, I get FC on App Helper. Same if I want to install anything.
- so I'm lost again... Any ideas?
Click to expand...
Click to collapse
I don't know. maybe your backup image was corrupted/
Aldo101t said:
I don't know. maybe your backup image was corrupted/
Click to expand...
Click to collapse
I actually made two backups and I tried the second one. I realized I didn't wipe cache and dalvik after installing stock recovery. I've flashed so many times tonight i'm going mad. Went in to stock recovery and wiped it, and upon reset and a lot of sweating it all works back to square 1.
Maybe I'll stick to stock... :silly:
Many thanks for the headsup on stock recovery. That's probably the only thing I hadn't tried and I wouldn't have thought of. :good::good::good:
http://forum.xda-developers.com/showthread.php?p=59896551
HTC ONE (M9) RUUs, OTAs, Stock TWRP Backups, Firmware & More Collection
---------- Post added at 01:13 PM ---------- Previous post was at 01:12 PM ----------
Rename it into 0PJAIMG.ZIP, put it on the ext sd card, reboot into 'download_mode', agree..
jauhien said:
http://forum.xda-developers.com/showthread.php?p=59896551
HTC ONE (M9) RUUs, OTAs, Stock TWRP Backups, Firmware & More Collection
---------- Post added at 01:13 PM ---------- Previous post was at 01:12 PM ----------
Rename it into 0PJAIMG.ZIP, put it on the ext sd card, reboot into 'download_mode', agree..
Click to expand...
Click to collapse
I have exactly the same issue, but can't get past the htc splash screen; any suggestions?
hellejoep said:
I have exactly the same issue, but can't get past the htc splash screen; any suggestions?
Click to expand...
Click to collapse
if you rename it OPJAIMG.zip before moving it to sdcard it will have two zips on it there(OPJAIMG.zip.zip)this will fail.
So I went to restore a previous ROM and the phone when I go to login is asking for my PIN (as usual). My previous PIN however isn't working. What do I need to do in the future before I make a backup so this doesn't happen again? Thanks.
EDIT: My guess is the data partition being encrypted is causing a problem...it's not a big deal if I don't recover this one but for the future so I know what went wrong?
You'd probably have to format storage in TWRP. Then flash a rom that supports having no encryption
I'm not sure if formatting the restoring a backup with encryption will work, though.
Nosferatu. said:
So I went to restore a previous ROM and the phone when I go to login is asking for my PIN (as usual). My previous PIN however isn't working. What do I need to do in the future before I make a backup so this doesn't happen again? Thanks.
EDIT: My guess is the data partition being encrypted is causing a problem...it's not a big deal if I don't recover this one but for the future so I know what went wrong?
Click to expand...
Click to collapse
boot back into twrp recovery- advanced - file manager-data-system-delete the files with the name locksettings.adb and 2 or 3more with locksettings file name
Appreciate it guys!
just data/system/lockscreen.db needs to be deleted. :good:
So I had the initial version of PA installed. Everything was working fine. I had the official TWRP.
- I tried to update via OTA but nothing was happening so I rebooted to recovery. A message showed up saying something like factory resetting data. Than it went into TWRP. I rebooted to system again to see if it actually factory resetted and it did. Someone mentioned in the PA thread that the message was in fact a text bug and that my phone factory reset because of the official TWRP.
- I've installed via fastboot blu_spark twrp. Wiped data,system,cache and dalvik. Installed new PA version, installed nano open gapps (arm64,v7.1) and latest SuperSU. It booted fine but when it asked for my google account, it didn't save it. The password was right, it just didn't want to accept it.
- I proceeded to install again, using same steps as above. This time i get message box constantly with google framework keeps closing, or something like that
- I assumed it's a twrp problem so I tried Arter97's twrp but still had the same issue
- I started flashing with different gapps, mini,nano,pico, even tried with previous version gapps from 9th of july, still same issue.
- After about 5 hours I gave up and flashed the latest stock zip. Booted fine, no force close, but gets stuck at "Just a sec", after you select your Wi-FI
I am not sure what to do next. Your help, would be much appreciated.
Here's a logcat I took. This is from last version of PA.
https://paste.ee/p/C19Ck
Edit: Another weird thing that happened is I tried to flash the latest OP3 firmware and twrp said something like "Your phone is OP3T and this firmware is for OP3".
I think your data partition maybe corrupted. But I'm not sure. Wait for someone with greater insight.
---------- Post added at 05:26 PM ---------- Previous post was at 05:23 PM ----------
Try one thing. Don't flash gaps at all. Then try with beans gaps if it works.
SOLVED
I formatted all partitions with fastboot and that did the trick.