Ran into this thread a couple days ago and decided to give it a try knowing the risk. I really don't like when information is held back for anything; just makes me want to know even more. Both the CM10 and AOKP JB ROMs softbricked my never used Amaze, and I don't want ICS when I'm running JB on my Inspire 4G. JellyBam also bricked my phone, but then I lost access to the internal SD (haven't tried an external). So I decided to try and unbrick my phone since I probably wouldn't get any help after so many warnings, and document the process. Now, it's booting fine so far but I still have no internal SD access, and I can share the steps I have been taking to fix it.
TYPICAL DISCLAIMER: I TAKE NO RESPONSIBILITY FOR WHATEVER MAY HAPPEN TO YOU OR YOUR PHONE IF YOU TRY THIS FIX!!!
I can see that JellyBam was ripped from other ROMs. The updater script is just the PACman ROM script (my Inspire's daily driver) with the printouts removed and a couple block names changed. And there are still some references to DHD/Inspire devices in some of the scripts... I had used hasoon's AIO toolkit to unlock, etc and used it to make sure I still had ADB access. So what I did was rip CM10's kernel and flash it with the AIO, and it booted! Now I just need to find a way to fix the SD issue which is probably just a bad mount in a script somewhere.
EDIT: I've also just checked the scripts for the CM10 and AOKP on a hunch, and they're the same as JellyBam. No wonder they all bricked my phone. The JB kernel isn't getting flashed in all these ROMs. And the random bricks I've been reading about could be because if the phone was running a Jellybean ROM before, it wouldn't brick. If not, then you have a brick.
Either you're doing some extensive research or just overlooked a simple process that's posted all over this Amaze Forum..
If you're not S-Off or using 4EXT Recovery w/smart flash on then no kernel will be flashed unless it's done manually.
That should be some of the basic knowledge when owning this phone.
Double0EK said:
Either you're doing some extensive research or just overlooked a simple process that's posted all over this Amaze Forum..
If you're not S-Off or using 4EXT Recovery w/smart flash on then no kernel will be flashed unless it's done manually.
That should be some of the basic knowledge when owning this phone.
Click to expand...
Click to collapse
OR use 4ext with SMARTFLASH enabled which will install the kernel when S-ON. This is the principal reason why 4ext is recommended for us AMAZE owners.
Update: sorry to regurgitate what you said. Didn't read it properly the 1st time.
HTC RUBY - Energized ICS Faux123 kernel - XDA APP Premium
You never mentioned what rom your "never used" Amaze came with. If it was still gb, then problems are inevitable just flashing a jb rom right away... If you already had a factory ics sense load on it, then you still face the above kernel issue/solution.
aokp is based in cm. And jellybam is based on aokp/cm. That's why all the scripts are similar. They all started with the cm base... Other phones might have had a straight aosp build before cm. Not the amaze. Cm was our first successful venture into jb.
I have flashed all of these ROMS and never had a softbrick...all roms booted and worked as advertised.
I am S-OFF...of course (its just a wire trick)
Lol ya, u said it yourself. No wonder they all bricked your phone. Good thing u had the hunch to check the scripts lmao
sent from my
NRGized amaze
powered by Faux
Double0EK said:
Either you're doing some extensive research or just overlooked a simple process that's posted all over this Amaze Forum..
If you're not S-Off or using 4EXT Recovery w/smart flash on then no kernel will be flashed unless it's done manually.
That should be some of the basic knowledge when owning this phone.
Click to expand...
Click to collapse
A little of both I guess. I was just comparing scripts from several ROMs to fix. My phone is still S-ON cuz I haven't gotten to that yet. I don't have enough time to do lots of reading. Usually I just read up on several of the most promising looking ROMs and settle with one as daily driver.
jeepers007 said:
You never mentioned what rom your "never used" Amaze came with. If it was still gb, then problems are inevitable just flashing a jb rom right away... If you already had a factory ics sense load on it, then you still face the above kernel issue/solution.
aokp is based in cm. And jellybam is based on aokp/cm. That's why all the scripts are similar. They all started with the cm base... Other phones might have had a straight aosp build before cm. Not the amaze. Cm was our first successful venture into jb.
Click to expand...
Click to collapse
The stock was GB, and there were no issues flashing ICS, so I dunno. And my point is that the script seems to originate in an entirely different (well, maybe not so different) phone's ROM with very little modification and cleanup.
In all this, all I'm doing is pointing out some stuff I observed. Don't get me wrong: I'm not bashing any developers; I have a lot of respect for each one. This is my 6th Android device incl 2 tablets, and I wouldn't've been happy without the XDA family and their fixes and custom ROMs. I just don't do this stuff a lot, and I don't really post unless I have a pretty big issue or something I think is very important. I just don't have that kind of time.
Skele Drew said:
A little of both I guess. I was just comparing scripts from several ROMs to fix. My phone is still S-ON cuz I haven't gotten to that yet. I don't have enough time to do lots of reading. Usually I just read up on several of the most promising looking ROMs and settle with one as daily driver.
The stock was GB, and there were no issues flashing ICS, so I dunno. And my point is that the script seems to originate in an entirely different (well, maybe not so different) phone's ROM with very little modification and cleanup.
In all this, all I'm doing is pointing out some stuff I observed. Don't get me wrong: I'm not bashing any developers; I have a lot of respect for each one. This is my 6th Android device incl 2 tablets, and I wouldn't've been happy without the XDA family and their fixes and custom ROMs. I just don't do this stuff a lot, and I don't really post unless I have a pretty big issue or something I think is very important. I just don't have that kind of time.
Click to expand...
Click to collapse
I think u missed the point. None of that is what caused your "soft brick." The only problem is that you are s-on, therefore when you flash a Rom the kernel does not get flashed.. unless you are using 4ext with smartflash enabled. It's not the scripts or anything causing issues, its the fact that u are s-on.
U need to either s-off or use 4ext with SF enabled then they will work fine
sent from my
NRGized amaze
powered by Faux
Finally fixed my phone. Everything should be fine now. Got full regular access to my internal SD again. I feel like kicking myself for the simple fix that it took though. For the past couple weeks I've been working on and off on a script to do an external flash. Debugging it has been giving me hell. And now I do a simple USB mount and format the storage on my computer, and it started working again...
Related
...a pain in the ass for the Fascinate. The gf has one of these phones, and after seeing what I've done with my G2, she wants me to root and flash a nice rom.
Problem 1 (not so small): we both use macs at home.
Problem 2 (huge): after reading through the development forum - it doesn't look that easy to root, nor flash a decent rom on the Fascinate!
not only do some roms require you to have a specific kernel flashed to use them. Some roms require that you don't use the latest CWM. Also, none of roms seem to be using Gingerbread AOSP completely. They seem to be pieced together with Froyo.
Believe you me, I am not a dev in the slightest. Therefore, I am looking for a safe way to root and flash a decent rom to her phone. If there isn't, then I'll just let her run stock.
Is this easier than I'm seeing it?
enserio said:
...a pain in the ass for the Fascinate. The gf has one of these phones, and after seeing what I've done with my G2, she wants me to root and flash a nice rom.
Problem 1 (not so small): we both use macs at home.
Problem 2 (huge): after reading through the development forum - it doesn't look that easy to root, nor flash a decent rom on the Fascinate!
not only do some roms require you to have a specific kernel flashed to use them. Some roms require that you don't use the latest CWM. Also, none of roms seem to be using Gingerbread AOSP completely. They seem to be pieced together with Froyo.
Believe you me, I am not a dev in the slightest. Therefore, I am looking for a safe way to root and flash a decent rom to her phone. If there isn't, then I'll just let her run stock.
Is this easier than I'm seeing it?
Click to expand...
Click to collapse
Honestly, it is not that difficult. Just takes some getting used to. Obviously you have done a bit of reading, I know it seems daunting, but I promise, once you have it down it is nothing. The kernels...Most ROMS are kernel switchable, within reason. MOST of our ROMS require the RED CWM, which honestly is not a big deal, the orange is just too glitchy. And as far as the ROM's being pieced together with Froyo...Well, I am no dev either, but yes, I believe most of the ROMS are a Frankenstein of sorts, but we don't even have a Froyo source to work with yet. So the dev's, in my opinion, have done an AMAZING job. In terms of flashing on a Mac, I am not sure if Odin works on a Mac, Heimdall does though I believe. Rooting is extremely simple, it is only the flashing the right CWM, modem, etc. that may confuse you. Honestly, if you just keep reading the right things, you'll see it is pretty simple. I recommend Adrynalyne's Super Clean 2.9, and Big Loof's Steel Blue theme, with the EB16 kernel (Also Adrynalyne's).
http://forum.xda-developers.com/showthread.php?t=948722
This thread has a good walkthrough, I'd follow it through Post #5... using Superclean. It's an incredibly performing full Froyo rom. Remember that Froyo is not officially out on this phone, she's running Eclair right now. Gingerbread is a ways off (though punk kaos is making great progress).
Before EB01, rooting for me was just clicking a single button.
I never had to root again since flashing EB01. For flashing itself, its just download, reboot to recovery, and flash. Not sure how its a pain in the as as it doesnt even take a minute or so.
I did end up installing 3.XX CWM from ROM manager, but I only reboot into orange CWM if i reboot using ROM manager. If I dont, I end up rebooting to red CWM.
Thanks for the responses. Put a few things in perspective. I totally forgot that she is still running Eclair and Froyo isn't officially out for these phones. My mistake, and now that makes complete sense to me why most of the roms are froyo based or patched. Another thing that made me hesitant is that Odin doesn't run on mac, and I would have anything to save the phone (unless I use one of the pcs at work) if something goes awry. I will read up on Heimdall and see if I can use that.
My apologies if I sounded bothered or uptight about the situation, thanks for the well-mannered responses to my mini-rant. Of to read up a bit more, starting with the link postd and Heimdall.
Found a quick guide for rooting the Fascinate with a Mac. Now my issue is...switching to EB01 without Odin because SuperClean needs it, correct?
I came from motorola phones so I'm used to locked bootloaders and the methods of hacking them. I've had the Rezound for almost 3 months now, and I'm currently running cleanROM 2.3. A few days ago I see we had a new ics leak, and from what I'm guessing, the rom bases have been updated for it. I'd like to flash the rooted leak, and install an ics rom, but I have a few questions. If I'm on ics already, what steps should I take? Do i have to go back to gb, and relock, or can I flash it through the current rom I'm on? Any advice is greatly appreciated!
Sent from my ADR6425LVW using XDA
Insidious said:
I came from motorola phones so I'm used to locked bootloaders and the methods of hacking them. I've had the Rezound for almost 3 months now, and I'm currently running cleanROM 2.3. A few days ago I see we had a new ics leak, and from what I'm guessing, the rom bases have been updated for it. I'd like to flash the rooted leak, and install an ics rom, but I have a few questions. If I'm on ics already, what steps should I take? Do i have to go back to gb, and relock, or can I flash it through the current rom I'm on? Any advice is greatly appreciated!
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
you don't have to go back to gb, but you do have to relock. as for the full instructions, they're somewhere on in the forum. searching helps. as for me, i'm got gonna update mine yet, so that's as far as i can help
Insidious said:
I came from motorola phones so I'm used to locked bootloaders and the methods of hacking them. I've had the Rezound for almost 3 months now, and I'm currently running cleanROM 2.3. A few days ago I see we had a new ics leak, and from what I'm guessing, the rom bases have been updated for it. I'd like to flash the rooted leak, and install an ics rom, but I have a few questions. If I'm on ics already, what steps should I take? Do i have to go back to gb, and relock, or can I flash it through the current rom I'm on? Any advice is greatly appreciated!
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
Wrong section bud, we have a Q & A
check out the 1st/2nd post on Wildstang's Twizted rom page. Very friendly instructions.
@mods - 'shut erdown
Ian
Here is the link from CleanRom to prepare you for new base ROMs:
http://www.scottsroms.com/showthread.php/856-HOW-TO-Prepare-for-CleanROM-4-0-Update?p=6527
It will take a while to flash and make sure you do reboot to boot loader the 2nd time so it flashes clean, but I would suggest backing up your SD card and internal storage. Good luck. I love the new leak, in the form of Clear ROM.
I'm having a bit of trouble updating my Rezound. I got the file named correctly and HBOOT detects it, however it loads/checks the RUU (blue/gold bars on the right) and then just goes back to the normal HBOOT menu without any error message or anything changing. I have relocked my Rezound.. Unsure of what else I can do. Any ideas?
You need to enter bootloader a second time for it to complete the full install.
It still isn't doing what it should be. It goes through loading/checking and then back into the normal bootloader menu. I then tried going into fastboot and back into bootloader, and the same process happened again. I also tried rebooting bootloader after it did the load/check process, but i'm not making any progress. By that, I mean it does the same exact thing.
After going through it the second time, what was the screen showing for your radio and hboot versions? Can't remember what the updated #'s off the top of my head but the radio should not be the .95### version.
Figured out the issue. I used an md5 checker and it came out wrong. guess I should try redownloading.. Must have gotten cutoff or something?
Sorry I got back so late, but thanks for the help everyone! Sorry about my post placement, I'm used to Droid forums and their Rezound section doesn't have a Q&A. Searching does help, but like I said, all of this dev support is a bit; overwhelming coming from a phone with little dev support, so people who can break it down for me are awesome.
Sent from my ADR6425LVW using XDA
Some advise
I will chime in and say that it is definitely worth it. As said before in the CleanROM thread Scott has a very detailed step by step guide. Just a few pointers before you jump in.
1) make sure you have a card reader for your computer that you can connect your removable micro-SD card to. Trust me, if you screw up somewhere in the process, having a reliable way to access the SD card is a life saver.
2) before flashing always wipe/factory reset 3 times, some think it is overkill, but if you end up with some odd glitch or bug when you just wiped once, you will most likely have to wipe and flash again to get rid of the bug...so of course you are actually saving time and hassle by just doing it 3 times in the first place.
3) make sure your battery is full or almost full before you start the process, you will avoid many problems by not having your phone battery die in the middle of a flash or update.
4) read, read and read again all the information and the instructions on what you are going to be doing, then make sure you understand and are comfortable Before you actually start. Reading through the forums and knowing beforehand what others have experienced, and the fixes, will make your life 100% better while you play with your phone.
All that said, the new RUU is awesome, better radio reception, better battery life for most (once you drain and recharge a few times), and ICS is very cool on the Rezound. Happy flashing people and hope you like ICS as much as I do.
I got rid of CWM Recovery the other day...Got into a Soft Brick using it...Not sure how it happened ...But got out of it none the least using the 1a Method from here...Loaded up TWRP...I would just like to know if I can flash any Rom using it ...It recomends 4 compatible ones...So Im just wondering if I can flash CM 9 or Virtuous...Or am I lookin at a Brick again if I do so...
Im currently runnin Gummy's which I really like but Im a Flashaholic...at least with my S2...And I know Ill do the same with the Prime...So just checkin ...
BTW never had a problem with CWM on my S2...And I flashed a Ton of Roms...Specifically ICS...
ronny71 said:
I got rid of CWM Recovery the other day...Got into a Soft Brick using it...Not sure how it happened ...But got out of it none the least using the 1a Method from here...Loaded up TWRP...I would just like to know if I can flash any Rom using it ...It recomends 4 compatible ones...So Im just wondering if I can flash CM 9 or Virtuous...Or am I lookin at a Brick again if I do so...
Im currently runnin Gummy's which I really like but Im a Flashaholic...at least with my S2...And I know Ill do the same with the Prime...So just checkin ...
BTW never had a problem with CWM on my S2...And I flashed a Ton of Roms...Specifically ICS...
Click to expand...
Click to collapse
There's a custom CWM recovery a guy posted that's supposed to have that issue fixed. I haven't tested it to a different problem with writing to my partition that's just due to an issue my prime had from the previous owner borking something. Recoveries are different on every device. I used CWM exclusively on my Thunderbolt, then I got the rezound and CWM wasn't worth having when it first came out officially, I only run Amon RA on there.
I also had the 1a "brick" which really wasn't anything more than a recovery loop. I've been using TWRP and I'm a flashaholic, and with Gummy, EOS, a CM9 build and AOKP plus a bunch of misc zip files I haven't had any problems with it. If you want me to test something let me know, I'm not at all scared to wipe a device as setup doesn't take me long at all
CharliesTheMan said:
There's a custom CWM recovery a guy posted that's supposed to have that issue fixed. I haven't tested it to a different problem with writing to my partition that's just due to an issue my prime had from the previous owner borking something. Recoveries are different on every device. I used CWM exclusively on my Thunderbolt, then I got the rezound and CWM wasn't worth having when it first came out officially, I only run Amon RA on there.
I also had the 1a "brick" which really wasn't anything more than a recovery loop. I've been using TWRP and I'm a flashaholic, and with Gummy, EOS, a CM9 build and AOKP plus a bunch of misc zip files I haven't had any problems with it. If you want me to test something let me know, I'm not at all scared to wipe a device as setup doesn't take me long at all
Click to expand...
Click to collapse
With the Galaxy s2 that I have I run CWM all the time...On Gingerbread Builds ...never a problem...On strictly ICS builds...never a problem...The problem came from flipping back and forth from GB to ICS...I had 3 soft bricks but got out thru Odin...Now with the newer versions of ICS builds you have to flash a different kernel or Odin it inorder to use CWM...thats to play it safe because there are enuff Hard Bricks that shows a problem...(Sumthin to do with The Framework in the newre ICS Roms)...So Im just careful when I flash...Don't need a Hard Brick...Im gonna stay away from CWM over here...especially the Touch Versions which gave us the first initial problems when flashin with CWM on the XDA Galaxy Forum here...
So Ill be usin TWRP and if its safe to flash the Roms you mention I should be okay...But like you state...every device is different...Ill just try to be careful and keep readin on here and see where the Bricks are cummin from when they occur...Thanx alot for the response...I appreciate it...
So did the S-off...Pretty painless using the unlimited.io site and some help from "Fuses" to asnwer a couple questions...did get the phone error where i oculdnt make calls, but sprint picks up when you call a number and they fix it for you. Does anyone have a link to flashing roms that i can read the threads instead of asking the process? I understand it, but would like to try flashing one before i restore all my apps and stuff..Thanks - And anyone that is worried about doing the s-off process, its actually pretty easy...
I think im confusing myself....so i did the s-off and when i looked at my phone "about" it said i was on version 3.15...i was told that i could flash my twrp backup from earlier today before i went s-off and all would be good, after i did it, phone restored good to go, but now it says im on version 3.16 - i guess i should have expected that, but i thought i would stay 3.15 for some reason!! I am totally confused now on how to flash a rom, any help or point me to the idiot guide would help, i understand, but still a noob and learning! The phone is still s-off so from what i have read, easy to recover should i screw up, downloading cm10.1 from goomanager right now and going to try and see what happends, i im assuming i can flash it from goomanager and flash the gapps right after...or am i missing a step?
tonyevo52 said:
I think im confusing myself....so i did the s-off and when i looked at my phone "about" it said i was on version 3.15...i was told that i could flash my twrp backup from earlier today before i went s-off and all would be good, after i did it, phone restored good to go, but now it says im on version 3.16 - i guess i should have expected that, but i thought i would stay 3.15 for some reason!! I am totally confused now on how to flash a rom, any help or point me to the idiot guide would help, i understand, but still a noob and learning! The phone is still s-off so from what i have read, easy to recover should i screw up, downloading cm10.1 from goomanager right now and going to try and see what happends, i im assuming i can flash it from goomanager and flash the gapps right after...or am i missing a step?
Click to expand...
Click to collapse
3.15 and 3.16 are linked to the base of the rom. If you flash a rom based on 3.15, It'll say 3.15. Same with 3.16.
As for flashing roms, just download the rom from it's thread, put it on your phone, wipe in twrp and flash the zip. I can't help with goomanager, never used it.
Thanks "End" ive looked for roms in here and on htcevo hacks, havent seen to many here to be honest, i might not be looking in the right place, any you would recommend? The ones on htcevo hacks all require gapps to be flashed afterwards, are the ones here the same...and again, sorry, just learning this stuff, still confusing at times!
tonyevo52 said:
Thanks "End" ive looked for roms in here and on htcevo hacks, havent seen to many here to be honest, i might not be looking in the right place, any you would recommend? The ones on htcevo hacks all require gapps to be flashed afterwards, are the ones here the same...and again, sorry, just learning this stuff, still confusing at times!
Click to expand...
Click to collapse
Have you checked these two whole forums?
http://forum.xda-developers.com/forumdisplay.php?f=1686
http://forum.xda-developers.com/forumdisplay.php?f=1594
Really depends on if you like Sense or prefer AOSP. I like sense so I'm using Viper4G 3.1.1. All Aosp roms require gapps to be flashed. Anything based on sense doesn't.
Good to go 714, tried the cm10.1 and didn't care for it, using Blue and Jazz right now.. Pretty cool.. Think I'll check out viper soon, heard it was good.. Thanks again...
Sent from my EVO using xda premium
Ok, so I'm going to start by saying that I am the furthest thing away from being an android noob, but this is my first Moto android device. I can see right away in terms of rom and kernel flashing it's a bit different than all the other android devices I've owned. I Picked up a RAZR for a really good price and it came loaded with Safestrap and had a 4.2.2 AOKP nightly loaded already on it. KI'm completely unfamiliar with bootstrap and how it works (I plan on reading up and learning everything today), but the guy that gave it to me said he accidently deleted the stock rom. To me, coming from all htc devices, I didn't think that was a big deal because who wants stock anyways? So, I'm not sure if it's critical to get that stock rom loaded back on in one of the slots or not.
I guess the point of this post is to see if anyone would care to share a couple helpful pointers for a first time moto user and hopefully make this learning process a bit easier.
Thanks to anyone who takes the time to reply with something other than "Read the stickies"
If you are happy with the AOKP, no need to install stock ROM. Stock ROM probably have less bugs, working 1080 camcoder, but lack options, that AOKP has.
localceleb said:
Ok, so I'm going to start by saying that I am the furthest thing away from being an android noob, but this is my first Moto android device. I can see right away in terms of rom and kernel flashing it's a bit different than all the other android devices I've owned. I Picked up a RAZR for a really good price and it came loaded with Safestrap and had a 4.2.2 AOKP nightly loaded already on it. KI'm completely unfamiliar with bootstrap and how it works (I plan on reading up and learning everything today), but the guy that gave it to me said he accidently deleted the stock rom. To me, coming from all htc devices, I didn't think that was a big deal because who wants stock anyways? So, I'm not sure if it's critical to get that stock rom loaded back on in one of the slots or not.
I guess the point of this post is to see if anyone would care to share a couple helpful pointers for a first time moto user and hopefully make this learning process a bit easier.
Thanks to anyone who takes the time to reply with something other than "Read the stickies"
Click to expand...
Click to collapse
Next time, make sure dont to delete the stock ROM, you can install other custom ROM on other ROM slots, make your stock rom as a backup if anything happens.
If you want to go back to stock ROM, or if your razr is bricked, i suggest you to download the fastboot file and flash the xml.zip you downloaded using RSD lite from the PC. Its just the same as 'Odin' if youre Samsung user. Download the fastboot file in the link given and also download rsd lite,you can google for it
http://sbf.droid-developers.org/umts_spyder/list.php
Sent from my GT-I9300 using xda app-developers app