I keep getting status 7 when trying to flash the newest Helly Bean that came out 12/27. I am coming from paranoid android and flashed to stock, flashed recovery fixed for cwm7 then try flashing that and keep getting status 7.
Edit: Nevermind.. Should probably check the bootloader option in odin.
Could a moderator closer the thread please?
Related
I've been using RemICS 1.3.1 ROM for a while. And now I'd like to upgrade to current 4.2.1 version but I'm getting Status 7 error: assert failed. I've found that I should try using Icy Glitch v14 kernel to flash a new rom but all links to this kernel are dead and I can't find it. Can someone help me to upgrade?
BTW: Should I expect some new bug on JB ? GPS is still not working there I guess...
lorendroll said:
I've been using RemICS 1.3.1 ROM for a while. And now I'd like to upgrade to current 4.2.1 version but I'm getting Status 7 error: assert failed. I've found that I should try using Icy Glitch v14 kernel to flash a new rom but all links to this kernel are dead and I can't find it. Can someone help me to upgrade?
BTW: Should I expect some new bug on JB ? GPS is still not working there I guess...
Click to expand...
Click to collapse
I had the same thing at some point last night as well, along with all the unknown upload mode errors and a series of other issues. The best advice I can give is to just keep trying different combinations.
I did end up going all the way back to stock a number of times. This might sound silly, but if I remember correctly, I successfully flashed ICZen and then I installed RemICS-JB from there. Had to swap the vold.fstab of course, but it's running very smoothly with RemICS-JB and Semaphore 2.9.
Sorry I couldn't be of more assistance, but with the amount of combinations and paths I tried, it's all a jumble.
Hi,
It gave me Status 7 error. Then I pulled the battery and rebooted into CWM. But after that it gave me freezed kernel screen
and I again did a battery pull and booted into CWM which was then converted to semaphore. Then I flashed the ROM again and gapps successfully
Hope this helps
tc
Hi all, only ever used Windows & Odin to flash Official/Leaked ROMs + Kernals. But have no access to a PC (Travelling round Thailand)
Anyway my phone keeps restarting when copy/pasting from chrome and maps so time to flash and new fancy 4.2 only lockscreen looks cool!
Currently on whatever the beta/leaked JB ROM was a few months ago.
Wanting this: http://forum.xda-developers.com/showthread.php?t=1850942
Hello there,
If you've flashed a custom kernel through Odin already, then you should be able to just download the 4.2.2 AOKP MR1 Build 4 zip and flash it through CWM, that is if you've flashed the custom kernel.
Let me know if you need more explaining.
With regards,
Beston94
beston94 said:
Hello there,
If you've flashed a custom kernel through Odin already, then you should be able to just download the 4.2.2 AOKP MR1 Build 4 zip and flash it through CWM, that is if you've flashed the custom kernel.
Let me know if you need more explaining.
With regards,
Beston94
Click to expand...
Click to collapse
Thanks, totally didn't enter my mind I could just flash it in CWM, lol.
Hello everyone. Ive been running the AOKP 1/22 JB ROM for a little while which I believe is 4.2.1 and wanted to try some other 4.2.2 jelly bean ROMs like cm10 and nexus ROM, but every time that I try to flash it I get an error 7. I remember running into this problem before but I don't remember the solution. Does it have to do about this new MALI driver I've seen mentioned so much? What is it? Please help!
Thanks
First, this should have been posted in the Q & A section.
Second, error 7 is a common issue which you should easily be able to learn about by searching.
It means the flashing firmware is checking the buildprop on your phone for phone model (I777) and finding a mismatch.
aspen1135 said:
Hello everyone. Ive been running the AOKP 1/22 JB ROM for a little while which I believe is 4.2.1 and wanted to try some other 4.2.2 jelly bean ROMs like cm10 and nexus ROM, but every time that I try to flash it I get an error 7. I remember running into this problem before but I don't remember the solution. Does it have to do about this new MALI driver I've seen mentioned so much? What is it? Please help!
Thanks
Click to expand...
Click to collapse
are you USED triangle away?always after it error 7 or flash stock ICS, flash siyah.tar-through Odin and then flash any roms!
Good luck!
aspen1135 said:
Hello everyone. Ive been running the AOKP 1/22 JB ROM for a little while which I believe is 4.2.1 and wanted to try some other 4.2.2 jelly bean ROMs like cm10 and nexus ROM, but every time that I try to flash it I get an error 7. I remember running into this problem before but I don't remember the solution. Does it have to do about this new MALI driver I've seen mentioned so much? What is it? Please help!
Thanks
Click to expand...
Click to collapse
Anytime I run into this issue, I revert to a really old backup (rooted-stock, CM, etc.) and then wipe and flash the ROM. That usually fixes it. Hopefully you have a backup that's compatible. If not, there's a thread around here that explains how to use Heimdell or something to flash a rooted-stock image that you can then use to update to the CM ROM.
It definitely can be done, and it's not too difficult. I've had to do it a time or two. Good luck!
aspen1135 said:
Hello everyone. Ive been running the AOKP 1/22 JB ROM for a little while which I believe is 4.2.1 and wanted to try some other 4.2.2 jelly bean ROMs like cm10 and nexus ROM, but every time that I try to flash it I get an error 7. I remember running into this problem before but I don't remember the solution. Does it have to do about this new MALI driver I've seen mentioned so much? What is it? Please help!
Thanks
Click to expand...
Click to collapse
Flash Siyah 4.3.3 kernel-> Reboot recovery-> Flash the 4.2.2 ROM zip -> You are good to go now.
Sent from my SGH-I777 using xda premium
---------- Post added at 01:30 PM ---------- Previous post was at 01:18 PM ----------
If you are already on Siyah 4.3.3 then Reboot into recovery-> Wipe data/factory reset, cache, dalvik-> Format system-> Reboot recovery-> Flash the 4.2.2 ROM zip. Hope this helps.
Sent from my SGH-I777 using xda premium
I constantly have this problem. I download my ROM of choice, open the zip, edit the updater-script, and delete the asserts inside for get.prop
Sent from my SGH-I777 using xda app-developers app
Well guys, I am a long time reader of the forum and have flashed just about every popular ROM I can find, but never posted before. Honestly I have been a little scared of posting questions because of how ruthless the 'veterans' can be on the noobs, but here I am. Anyway, so far I have stuck with JellyBeans 17 and LOVE it. I haven't had any issues at all till now. Since a few days ago, I keep getting a notification that there is an OTA update available, for Beans I am assuming. When I try to download/update, it does not happen even though my phone auto-reboots into recovery, flashes something, then auto-reboots the system.
Right now my OTA Updater is telling me there is an update available, and when I click to download this is what happens:
-Prompt to wipe cache, which I do, then click download
-Download meter appears (0/100) but never fills, then
-Reboots into TWRP (v2.5.0.0)
-Flashes something (update?)
-Reboots system
-Continues to prompt me that there is an update available in notification bar
Running JB17 and TWRP 2.5.0.0
Checking for updates in ROM Toolbox and GooMgr says NO updates available for me. Plus, the only compatible ROMs browsing 'finds' for me are CM, carbon, and liquidsmooth.
Questions:
Should I update TWRP to the latest (2.5.0.3)?
What is the deal with the OTA updater not functioning correctly? Should I not use this?
Thank you guys, and please take it easy on this gal . I learned my way around XDA and rooting by reading a ton of stuff and through trial and error. I may be a new poster, but I'm not so new to rooting and flashing ROMs. I am still learning all I can, and open to any and all suggestions. Totally addicted to customizing my Note2.
Since you are on beans, yes the OTA is for beans rom. It is nice that he included this for updating his rom, unfortunately there have been issues with it for the past few builds. If you want to update to the newest build, go to his rom thread and download b18. Then boot into recovery and flash b18. You don't need to update twrp to the newest version. Twrp 2.5.0.0 works just fine for it. For future reference, this should have been posted in beans rom thread
Link to beans thread
http://forum.xda-developers.com/showthread.php?p=5617585
BoostedB18C said:
Since you are on beans, yes the OTA is for beans rom. It is nice that he included this for updating his rom, unfortunately there have been issues with it for the past few builds. If you want to update to the newest build, go to his rom thread and download b18. Then boot into recovery and flash b18. You don't need to update twrp to the newest version. Twrp 2.5.0.0 works just fine for it. For future reference, this should have been posted in beans rom thread
Link to beans thread
http://forum.xda-developers.com/showthread.php?p=5617585
Click to expand...
Click to collapse
I wish I could have posted in the Beans thread, but since my post count is what it is, the forum will not allow me to until I hit 10. Sorry...
Stupidly I updated to jelly bean through the Asus ota a while back and have recently decided it is sluggish and terrible. I have root and a custom recovery (TWRP) but it seems flashing an ICS ROM will give me a soft brick.
This isn't urgent, I can restore back to jelly bean using my back ups. But is there anything special that needs to be done to revert back to ICS?
I have been doing what I think is kind of the usual for flashing Roms .
Full wipe
Flash ROM
Flash gapps
Sent from my SGH-I337 using xda app-developers app
From my limited experience with Tf201, I read that to avoid a brick its important to flash the correct bootloader and recovery first? Not sure which though. You can also install Nvflash for Jellybean TF201 which apparently makes the device ’unbrickable’, theres a thread on this forum how to do it. Also, before you downgrade, try the unofficial cyanogenmod 4.3 jelly bean rom. Its very smooth and fast compared to the ota official Asus official JB, which is terrible as you said.
rust991 said:
Stupidly I updated to jelly bean through the Asus ota a while back and have recently decided it is sluggish and terrible. I have root and a custom recovery (TWRP) but it seems flashing an ICS ROM will give me a soft brick.
This isn't urgent, I can restore back to jelly bean using my back ups. But is there anything special that needs to be done to revert back to ICS?
I have been doing what I think is kind of the usual for flashing Roms .
Full wipe
Flash ROM
Flash gapps
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
You cannot go back to ICS unless you have nvflash backups.
You can now create nvflash backups while you are on Jellybean tho which you couldn't do before.
I would advise trying one of the Hairybean Roms which is a big improvement over stock. If you do not want to go to the latest one you can flash Hairybean 1.51 which will flash ok on your bootloader and recovery without you changing anything.