I don't have enough posts here to be allowed to post this in the development forum, so I figured this might be a place to ask about my issue.
I have a MZ602 (4G) and was coming from rooted ICS 4.0.4. I used TWRP and wiped cache, dalvik and system. I flashed the latest nightly (120) and GAPPs (O8120802-eos-signed.zip). When I rebooted, all looked okay except, I could not unlock. Camera works, Google works (it loads. I am obviously not online ). I double checked the MD5s and they were correct. Same problem when I flashed with the 119 nightly.
Any ideas?
Wipe data.
Sent from my SGH-I747 using xda premium
Tried that with no change. Also tried earlier nightly and Gapps, also no change.
From recovery, wipe all, format system , flash ROM again...
Sent from my MZ601 using Tapatalk 2
Thanks,:good: I have tried that, but that doesn't mean I don't appreciate your help. This stuff will definitely make us nuts.
Wipe everything via fastboot then try to reinstall.
Sent from my Galaxy Nexus using xda premium
d3athsd00r said:
Wipe everything via fastboot then try to reinstall.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
My entire experience with fastboot was unlocking the bootloader on my Xoom. So I don't speak much fastboot. What are the commands I would need to do a wipe using fastboot and would it hamper my ability to restore my nandroids?
Thanks
I have the same problem and have tried the same things you have with no success.
iosmacman said:
I have the same problem and have tried the same things you have with no success.
Click to expand...
Click to collapse
Out of curiosity which recovery did you use to flash? I was using TWRP.
Another poster in the Developer Forum, happysteve11c , has this result too. So, perhaps we all did something similar. I was wearing my lucky shirt and waited until mercury was in retrograde before trying to flash, so it should have worked.
Related
I just flashed the MXH Superlite rom (http://forum.xda-developers.com/showthread.php?t=1525638&page=43) as per the instructions onto my skyrocket i727. Wiped it, cleared dalvik cache and formatted the system. Installed the recommended modem followed by the rom, and the phone was stuck on the Samsung startup screen. I've recovered using a backup, but I really want to install this rom. Whats the problem here?
Try booting into cwm and re wipe and reinstall, try just the rom this time
Sent from my SAMSUNG-SGH-I727 using xda premium
I was gonna flash this ROM later tonight have other ppl had issues?
Sent from my SAMSUNG-SGH-I727
droid512 said:
I was gonna flash this ROM later tonight have other ppl had issues?
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
Your best bet is review the MHX-SUPERLITE thread in the Development section... and ask there. This rom is on my "next to flash" list as well...
I flashed it on a friends sr no issues but it progressively got slower and crawled after first reboot it was odd.
Sent from my SAMSUNG-SGH-I727
droid512 said:
I flashed it on a friends sr no issues but it progressively got slower and crawled after first reboot it was odd.
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
Mhx will say its cuz he is stuck developing on a non apple device
Sent from my SAMSUNG-SGH-I727 using Tapatalk
You need to wipe everything a couple times before flashing on these phones and sometimes install 2-3 times too
Wipe data, cache partition, and delvik 3x's each and install twice or something
Non-bricked Skyrocket since 2-11-2012
I've never once installed multiple times multiple wipes yes but multiple installs????
Sent from my SAMSUNG-SGH-I727 using Tapatalk
safzal433 said:
I just flashed the MXH Superlite rom (http://forum.xda-developers.com/showthread.php?t=1525638&page=43) as per the instructions onto my skyrocket i727. Wiped it, cleared dalvik cache and formatted the system. Installed the recommended modem followed by the rom, and the phone was stuck on the Samsung startup screen. I've recovered using a backup, but I really want to install this rom. Whats the problem here?
Click to expand...
Click to collapse
Try Flashing a different Kernel
What I do every ROM flash and never an issue.
1. Flash Darkside
2. Flash Modem (if I'm changing)
3. Flash ROM
4. Reboot
Sent from my SAMSUNG-SGH-I727 using xda premium
Usually I just wipe data, cache, and dalvik. Today though I did this plus formated data, cache, and system. I never do this but the JellyWiz rom I was flashing said to do so. Since I did this the rom will not flash.
E: Can't open /external_sd_Root/Incubus26jc_JellyWiz_VZW_9_14_12_RLS3.zip (bad)
Installation aborted.
Click to expand...
Click to collapse
When I tried restoring the old JB version I was updating from it gave me a MD5 mismatch error. When I tried to restore my original stock root which I have restored from several times without issue it just gave me "Error while restoring /system."
Need help! Stuck in recovery with no idea what to do
Try flashing a firmware through odin: 0
sent from my Galaxy s3 GT i9300 using xda premium HD @ jelly bean leaked builds
i9100g user said:
Try flashing a firmware through odin: 0
sent from my Galaxy s3 GT i9300 using xda premium HD @ jelly bean leaked builds
Click to expand...
Click to collapse
Not really sure what this means to be honest. I rooted using odin but what do you mean by flashing a firmware?
josbor11 said:
Not really sure what this means to be honest. I rooted using odin but what do you mean by flashing a firmware?
Click to expand...
Click to collapse
Yes, do that again. Boot into Download mode(Batt pull to turn the phone off) then hold vol down+home+power till the prompt comes up.
Flash the root66 image using Odin from there.
Brian Gove said:
Yes, do that again. Boot into Download mode(Batt pull to turn the phone off) then hold vol down+home+power till the prompt comes up.
Flash the root66 image using Odin from there.
Click to expand...
Click to collapse
I can just flash 66 as is? Don't have to flash a stock unrooted version first like you do when you brick?
Do you have any idea why this could have happened? I did everything it said on the page and even watched an installation video for the ROM following every step by step instruction. What the hell does formatting system, data, and cache do in recovery? Never had done it before and as soon as I did my phone just messed up. Also, if I flash 66 using odin will my old backups work again?
josbor11 said:
I can just flash 66 as is? Don't have to flash a stock unrooted version first like you do when you brick?
Do you have any idea why this could have happened? I did everything it said on the page and even watched an installation video for the ROM following every step by step instruction. What the hell does formatting system, data, and cache do in recovery? Never had done it before and as soon as I did my phone just messed up. Also, if I flash 66 using odin will my old backups work again?
Click to expand...
Click to collapse
I'm guessing there was a bad download and sadly your nandroid might have been corrupted.
Yes if you flash root66 hopefully your backups will work if they aren't corrupted.
Sent from my Galaxy Nexus using xda app-developers app
voodoomanx said:
I'm guessing there was a bad download and sadly your nandroid might have been corrupted.
Yes if you flash root66 hopefully your backups will work if they aren't corrupted.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Cool thanks. Flashing 66 now through odin. My backups have worked fine before (the exact same ones that just failed). Once this is finished and I test out my backups (assuming they work) how should I go about reflashing JellyWiz? Should I format the system, data, cache again or just do the normal wipes? I'm afraid formatting will mess it up again. Is CWM inferior to TWRP? Thinking about using a different recovery after all of this.
josbor11 said:
Cool thanks. Flashing 66 now through odin. My backups have worked fine before (the exact same ones that just failed). Once this is finished and I test out my backups (assuming they work) how should I go about reflashing JellyWiz? Should I format the system, data, cache again or just do the normal wipes? I'm afraid formatting will mess it up again. Is CWM inferior to TWRP? Thinking about using a different recovery after all of this.
Click to expand...
Click to collapse
I personally use cwm and to me it's more a matter of preference. I too have had a error restoring backups once and it was after a system wipe. A word of advice, because this saved me, keep a ROM on your SD card at all times to be able to just flash in an emergency.
Sent from my SCH-I535 using xda app-developers app
kintwofan said:
I personally use cwm and to me it's more a matter of preference. I too have had a error restoring backups once and it was after a system wipe. A word of advice, because this saved me, keep a ROM on your SD card at all times to be able to just flash in an emergency.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
A rom of Root 66?
Is it cwm flashable? I keep synergy as an emergency backup.
Sent from my SCH-I535 using xda app-developers app
josbor11 said:
A rom of Root 66?
Click to expand...
Click to collapse
dont listen to him...flash root66 thru odin as already mentioned and go from there...use my guide if need be.
droidstyle said:
dont listen to him...flash root66 thru odin as already mentioned and go from there...use my guide if need be.
Click to expand...
Click to collapse
I think you missed my point, at this point he needs Odin. However, if you keep a zip on your SD card then if your backups gasp like his situation he can just fish that zip. It was simply some advice for future reference, were not all next to a computer ask the time. For people like me that just get an urge to flash it helps to have backups like this.
Sent from my SCH-I535 using xda app-developers app
No one is addressing the format question originally asked. Why is formatting being requested on yhe newer jb rom's, and what (in detail) does it do?
Many posts that people are soft bricking thier devices because of formatting instead of just wiping.
What's the deal, want some real answers here, and I think many others do too.
Sent from my SCH-I535 using xda premium
annoyingduck said:
No one is addressing the format question originally asked. Why is formatting being requested on yhe newer jb rom's, and what (in detail) does it do?
Many posts that people are soft bricking thier devices because of formatting instead of just wiping.
What's the deal, want some real answers here, and I think many others do too.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
in order to flash jellywiz i had to do the following or else i bootlooped:
wipe data/factory reset
wipe dalvik cache
format system
flash rom
booted up flawless.
i also used this methid for paranoid android...i will probably update my guide with this. unfortunately i cant give any info on what formatting system is actually doing. never had to do this before??
annoyingduck said:
No one is addressing the format question originally asked. Why is formatting being requested on yhe newer jb rom's, and what (in detail) does it do?
Many posts that people are soft bricking thier devices because of formatting instead of just wiping.
What's the deal, want some real answers here, and I think many others do too.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I don't know why they are suggesting it but it doesn't do anything beyond the normal factory reset and then the zip formatting system itself.
Its just the manual way of doing what a clean flash does.
Why are people having issues restoring nandroids after doing this? Apparently bootlooping occurs after format/jb install/restore previous nandroid.
Sent from my SCH-I535 using xda premium
Brian Gove said:
I don't know why they are suggesting it but it doesn't do anything beyond the normal factory reset and then the zip formatting system itself.
Its just the manual way of doing what a clean flash does.
Click to expand...
Click to collapse
if im not mistaken formatting the system deletes the rom/kernel itself...normal factory reset from cwm recovery only deletes rom data/cache.
---------- Post added at 09:06 PM ---------- Previous post was at 09:03 PM ----------
annoyingduck said:
Why are people having issues restoring nandroids after doing this? Apparently bootlooping occurs after format/jb install/restore previous nandroid.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
edit* good question!
droidstyle said:
if im not mistaken formatting the system deletes the rom/kernel itself...normal factory reset from cwm recovery only deletes rom data/cache.
Click to expand...
Click to collapse
Yeah you're right but the zip of the ROM 99% of the time formats system also.
Brian Gove said:
Yeah you're right but the zip of the ROM 99% of the time formats system also.
Click to expand...
Click to collapse
i wonder why i had to format system to get the latest jellywiz rom to not hang on galaxy s splash screen? it makes no sense.
Also, how does a format not erase your nandroids? It should also wipe titanium backups if they are not on your external. Am I wrong on that? Could formatting lose certain bits of info that the nandroid may not have partitioned, and that's why the restores are not working correctly?
Sent from my SCH-I535 using xda premium
---------- Post added at 09:57 PM ---------- Previous post was at 09:55 PM ----------
Add on: good info guys
Sent from my SCH-I535 using xda premium
I have an AT&T One XL and have had problems recently. I unlocked my bootloader last year on the 2.20 firmware, which is how the phone came. I was able to flash ROMs no problem. About 3 weeks ago I decided to go S-Off with the whole thing. The S-Off was successful, I immediately flashed a new splashscreen and it is confirmed in bootloader that I am S-off. Last week I tried to flash the stable CM10 build, but it was unsuccessful. I found that the only ROMs I am able to flash are Sense ROMs 4.1.1 and above, or AOSP ROMs that are 4.2.x or above. I am on hboot 1.14 and I am very confused as to why I cannot flash properly. I am on TWRP 2.4.1.0, but have used various recoveries trying to solve the problem. I have also RUU'd trying to fix the problem, but to no avail. Any help would be much appreciated!
Twrp 2.4 has issues with wiping properly. Have you tried a different version or wiping with adb in fastboot?
Sent from my HTC One X using xda premium
From what I understand twrp 2.4.1 should be working but I would flash 2.3.x just in case, then do fastboot erase cache. Then wipe cache, dalvik, system, factory reset.
If you RUUd and are s-off why are you still on 1.14? You may as well go up to 2.14 then downgrade touchscreen to use AOSP. Super easy.
Since S-OFF is just a security flag, I am 100% sure it's not the cause of your issue.
Sent from my One X using xda app-developers app
exad said:
From what I understand twrp 2.4.1 should be working but I would flash 2.3.x just in case, then do fastboot erase cache. Then wipe cache, dalvik, system, factory reset.
If you RUUd and are s-off why are you still on 1.14? You may as well go up to 2.14 then downgrade touchscreen to use AOSP. Super easy.
Since S-OFF is just a security flag, I am 100% sure it's not the cause of your issue.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I haven't wiped in fastboot because I thought that's what wiping in recovery was for, I really appreciate all of the input and I will be trying both of these things as soon as I'm done with dinner. Man's gotta eat, ya know :laugh:
Lol. Yep.
Sent from my HTC One X using xda premium
Only fastboot erase cache! The rest of the wiping is done in recovery!
Sent from my One X using xda app-developers app
exad said:
Only fastboot erase cache! The rest of the wiping is done in recovery!
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
As a question, what is the difference between wiping cache in recovery and the fastboot command?
Downgrade twrp to 2.3.3.1
Sent from the HOXL dimension of S-OFF
The fastboot command wipes a cache related to the recovery. Wiping cache in recovery wipes a cache relating to the rom.
Sent from my One X using xda app-developers app
exad said:
The fastboot command wipes a cache related to the recovery. Wiping cache in recovery wipes a cache relating to the rom.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
So I wiped cache via fastboot, and flashed the ROM like i normally would (wipe everything in recovery), but nothing has changed. I still get hung up on the splashscreen when trying to boot the new ROM. ViperXL boots fine when I restore my NANDroid backup, though.
Did you try flashing the boot.img after? You're still on hboot 1.14 afterall. I haven't seen first hand if you can skip flashing the boot.img with s-off, in your case, it seems not.
Sent from my One X using xda app-developers app
exad said:
Did you try flashing the boot.img after? You're still on hboot 1.14 afterall. I haven't seen first hand if you can skip flashing the boot.img with s-off, in your case, it seems not.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Even without flashing the boot.img, it should go past the splashscreen to the boot animation, am I wrong?
You are wrong. It may depending on the kernel previously installed
Sent from my One X using xda app-developers app
exad said:
You are wrong. It may depending on the kernel previously installed
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Sorry to sound like a complete noob, I've been rooting ect for 2.5 years and never seen this problem. Could you please explain a bit more what you mean by the previous post. Are you saying it's the kernel or the boot.img not being installed correctly?
WeiblezWobble said:
Sorry to sound like a complete noob, I've been rooting ect for 2.5 years and never seen this problem. Could you please explain a bit more what you mean by the previous post. Are you saying it's the kernel or the boot.img not being installed correctly?
Click to expand...
Click to collapse
flashing the boot.img is flashing the kernel. you don't sound like a complete noob so don't worry.
I'm going to try again right now to flash the boot.img and then the ROM like normal, reporting back in 15 mins
WeiblezWobble said:
I'm going to try again right now to flash the boot.img and then the ROM like normal, reporting back in 15 mins
Click to expand...
Click to collapse
wipe everything first of course. cache dalvik system and factory reset. i dont mean to treat you like a noob but its better to be extra specific than not specific enough
exad said:
wipe everything first of course. cache dalvik system and factory reset. i dont mean to treat you like a noob but its better to be extra specific than not specific enough
Click to expand...
Click to collapse
Alright, tried it all exactly how you said and it had the same response, got stuck on splashscreen. I am completely puzzled
WeiblezWobble said:
Alright, tried it all exactly how you said and it had the same response, got stuck on splashscreen. I am completely puzzled
Click to expand...
Click to collapse
alright so just to be sure. first off youre on twrp 2.3.x right?
you wipe cache, dalvik, system and factory reset right?
then you flash the rom and the boot.img right? (doesnt matter what order these are flashed)
and still bootlooping?
exad said:
alright so just to be sure. first off youre on twrp 2.3.x right?
you wipe cache, dalvik, system and factory reset right?
then you flash the rom and the boot.img right? (doesnt matter what order these are flashed)
and still bootlooping?
Click to expand...
Click to collapse
Exactly, but just to be 100% clear, I am getting stuck at the splashscreen, and it just sits there infinitely.
My brother just got himself a skyrocket he's on the newest radio w/custom recovery installed but can't seem to flash anything but cm 10.1 with an old 4.2 GApps package.
Kinda frustrating because I haven't seen anyone else having this issue in any other thread. I did to his all I did to mine and I'm running Wantowan2's DU. Just says installation failed and we can't even flash other recovery from within recovery. Where should we go from here
Sent from my SGH-I727 using xda app-developers app
Odin back to stock and start over. Something got messed up in your recovery
Make sure you've got the proper recovery for 4.3 as well.
Sent from my SGH-I727
Well we did Odin back to stock and Odin flashed twrp 2.6.3 and tried to flash the new cwm touch 6043 and it just failed. Not sure why. I repeated process with my phone and it worked but I feel like he did some stuff he's not telling me.
And the only things that do flash remain to be the cm 10.1.3 and GApps from 2012
Sent from my SGH-I727 using xda app-developers app
K
Boot_Derran said:
Well we did Odin back to stock and Odin flashed twrp 2.6.3 and tried to flash the new cwm touch 6043 and it just failed. Not sure why. I repeated process with my phone and it worked but I feel like he did some stuff he's not telling me.
And the only things that do flash remain to be the cm 10.1.3 and GApps from 2012
Sent from my SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
The gapps isn't right for 4.3, cm 10.1. Flash the 8-13-2013 gapps
Edit, you can find it on the OP of this http://forum.xda-developers.com/showthread.php?p=46685423
My understanding is that cm 10.1.3 is android version 4.2.2 and the gapps he used worked. No force closes or anything but one thing he mentioned is that his first flashing of the ROM did not include a full wipe. He did not format system. And even after a full wipe in twrp 2.6.1; data, cache, android secure, dalvik, and system still nothing. Still shows dead android and failed install
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Boot_Derran said:
My understanding is that cm 10.1.3 is android version 4.2.2 and the gapps he used worked. No force closes or anything but one thing he mentioned is that his first flashing of the ROM did not include a full wipe. He did not format system. And even after a full wipe in twrp 2.6.1; data, cache, android secure, dalvik, and system still nothing. Still shows dead android and failed install
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
What is the exact error message that TWRP is giving?
Gotta wait for my bro to get off work but will post as soon as I can get his phone and give it another go
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Hi,
I just downloaded and installed the full update for my Shield Tablet ROW LTE and it seems incomplete. I did a full wipe (via TWRP) before installing and the install seemed to go OK, but when I reboot i get a screen like in the pic attached (sorry for poor quality). No nav bar at bottom, no notification bar, no wall paper, no lockscreen. Any ideas what could be the problem? I've reinstalled a few times but no luck.
Thanks for any help.
Are you sure you loaded the correct file?
Have you tried a factory reset?
Otherwise, try to clear cache in TWRP recovery and reinstall the rom?
Sent from my SHIELD Tablet using XDA Free mobile app
An Droid said:
Are you sure you loaded the correct file?
Have you tried a factory reset?
Otherwise, try to clear cache in TWRP recovery and reinstall the rom?
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
Dude the SAME thing happened to me just today! Flashing old backups, and the OTA files, the problem persists.
Edit: Actually, I switched to CWM, and it worked just fine... I can only imagine it has something to do with /boot, which as far as I know you can't wipe in TWRP.
Which version of TWRP are you guys using? The one based on v.2.8.2.0 or v.2.8.5.0?
If v.2.8.5.0, try the v.2.8.2.0 instead as some have reported problems with v.2.8.5.0.
Sent from my SHIELD Tablet using XDA Free mobile app
An Droid said:
Which version of TWRP are you guys using? The one based on v.2.8.2.0 or v.2.8.5.0?
If v.2.8.5.0, try the v.2.8.2.0 instead as some have reported problems with v.2.8.5.0.
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
Nope I had the issue with 2.8.2.0, the 2.8.5.0 build doesn't even work for me haha.
I guess I'm sticking with CWM for now >.>
I'll try CWM using latest TWRP and continues to fail. I am definitely using the correct update zip.
Sent from my HTC One_M8 using Tapatalk
An Droid said:
Are you sure you loaded the correct file?
Have you tried a factory reset?
Otherwise, try to clear cache in TWRP recovery and reinstall the rom?
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
Did factory reset, definitely correct update zip, reinstalled at least ten times, wiping cache etc. Nothing works. Will flash cwm later and try with that
Sent from my HTC One_M8 using Tapatalk
OK, to update I tried CWM and both versions of TWRP to no avail. I had to download the full LTE RoW Recovery OS Image and flash it via fastboot and now all is well. Thanks for the comments and suggestions.