Database Develop

[GUIDE] Injecting CWM into any kdz update

Hey guys,
I've managed to devise a method to inject the CWM recovery image into the LG Update tool during updating with a kdz.
The basic idea is explained in this post. I took it a bit further. During the updating process, you can replace the recovery image inside the updater's memory. Basically, you can use this method on any LG Updating tool. This guide uses KDZ Updater. The method is great for getting the latest firmware for your region and still get it rooted.
This procedure requires some quick actions in order to succeed. Read through it before attempting to flash. I'm not responsible for anything that might happen in the result of using this guide.
Needed files:
CWMInject
UPK
Latest CWM recovery image for P970
Cheat Engine
1. Run KDZ Updater from UPK with Windows Enabler on.
Select your KDZ file.
2. Run CWMInject with Admin privileges. Select KDZU process. Set CWM image to the recovery image file.
3. Run Cheat Engine. Select KDZU process. Change Value Type to Text and write ANDROID! in the search field.
4. Open Task Manager, go to Processes and sort processes by memory.
5. In KDZ Updater, press Launch software update.
6. Keep an eye on the KDZU process in Task Manager, if it starts growing, it means it has started to load the files into memory and you can move to the next step.
7. In Cheat Engine, press First Scan. If it doesn't find anything, you did this too early. It should find 3 addresses. The last one is what you need.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
8. Copy the found address to CWMInject and press Write Memory. This needs to be done as quickly as possible from the time of finding the addresses.
9. Finish flashing.
Now your phone has CWM recovery installed. You can get into it with "adb reboot recovery". You need the Android SDK for that.
To root your phone, put this Superuser.zip on your SD card and use CWM to flash it.
You don't necessarily have to use KDZ Update. I tried this method with R&D Test Tool and the regular LG Mobile software update. You just need the right process name for CWMInject and Cheat Engine.

That is excellent man. Bin files? Nobody need it anyway. Lol. Profit!
Sent from my LG-P970 using XDA App

Updated the first post with the guide. Cheers

Confirmed, working with V20F from Orange Romania, using R&D Tool.
CWMInject.exe needs to be run as administrator, in case you're using Win as a non-privileged user.
As an interesting sidenote, I forgot to do a factory reset before (coming from Zeus v4.01b), so I got a bootloop. Easy way to get rid of that: flash a V10 based firmware, it won't recognize the ext4 data partition -> no bootloop. Did a factory reset from there, then repeated the flashing for V20F. Worked like a charm.

Amazing!!!!!!

Awesome! With R&D... the process is "LGUserCSTool". After flashing it boots directly to CWM.
CSE Web upgrade test: (Small server)(for a factory reset)

Flashed V20N with R&D.
It works like a charm. Thank you very much.

Great to see it working for everybody!
If you're feeling adventurous, you can test my updated CWMInject. It has a built in memory scanner, so you can just press Start after you've started updating.
Edit:
Oh yeah, it requires .Net Framework 4 now...

roltzy said:
Great to see it working for everybody!
If you're feeling adventurous, you can test my updated CWMInject. It has a built in memory scanner, so you can just press Start after you've started updating.
Edit:
Oh yeah, it requires .Net Framework 4 now...
Click to expand...
Click to collapse
Very nice. I guess the Cheat Engine is no more required.
ETA: maybe it would be a good idea to specify in the manifest that it requires admin privileges.

Yeah, good idea.
I guess not everybody disables UAC as the first thing after installing Windows

gabwerkz said:
Awesome! With R&D... the process is "LGUserCSTool". After flashing it boots directly to CWM.
CSE Web upgrade test: (Small server)(for a factory reset)
Click to expand...
Click to collapse
I have a Question!... When is the best moment to aply CWMInject?? i want to use R&
__________________________
i solve the question, really works so great!!!

I've usually applied it around the 10% mark, so it gets done at 16% or so. It's worked every time, for all the updating software, since the underlying flashing process seems to be the same for each one.

Yeah, it works very well and together with this trick http://forum.xda-developers.com/showthread.php?t=1473781 you can now flash KDZ if it is not for your region.

Didnt work with V20B_00.kdz for India
I did everything as stated in the first post. The Memory of recovery-clockwork-touch-5.8.1.3-p970 was also injected successfully within 10% of flashing. And phone rebooted with new the rom. However, I am not able to get into the CWM. I tried the vol+ hard key while booting, but CWM is not coming. Help!

advptg said:
I did everything as stated in the first post. The Memory of recovery-clockwork-touch-5.8.1.3-p970 was also injected successfully within 10% of flashing. And phone rebooted with new the rom. However, I am not able to get into the CWM. I tried the vol+ hard key while booting, but CWM is not coming. Help!
Click to expand...
Click to collapse
roltzy said:
Hey guys ...
Now your phone has CWM recovery installed. You can get into it with "adb reboot recovery". You need the Android SDK for that...
Click to expand...
Click to collapse
for short messages

What is this for?
What is this Android SKD? how is such injection of CWM useful?

It is simple. With CWM injection you can root every KDZ. And with KDZ firmware update fix, you can use R&D Tool and flash KDZ to your phone.

Nice thread.. My sister just got an optimus black, ( And i want to root it) does this method should be with the phone on download mode or what ??
Not very familiar with the way optimus root process is done. I own a GS2
EDIT: Well I did with the phone ON, and USB debug mode ON,/ OFF, also have tried doing [Remove battery,sim,SD] hit vol up and inert the usb cable to enter in download mode.. But always when I click Launch Software Update when it starts to decompress the KDZ file it just got frozen, and (Not Responding)
Any clue ? I´m trying to root a v20a (mexican) version.
Thanks.

I can't open CWMInject, I'm on Windows XP...

not what I did wrong, now my phone does not start this brick

[Fastboot] Droid Razr M Xt907 Ice Cream Sandwich

DROID RAZR M XT907 Ice Cream Sandwich software update availability​
The following table is for reference only.
Country|Carrier Name|Android|System version
US|Verizon|4.0.4|Blur_Version.77.111.10.XT907.Verizon.en.US
BUILT PROPERTIES
build.id=7.7.1Q-144_SMQ_S136-10
build.version.release=4.0.4
build.date=Mon Aug 27 06:18:07 CDT 2012
Blur_Version.77.111.10.XT907.Verizon.en.US
Click to expand...
Click to collapse
Click to expand...
Click to collapse
1. 7.7.1Q-144_SMQ_S136-10 - Verizon
Source: http://www.droidevelopers.com/showt...e-Cream-Sandwich-software-update-amp-download

mine tried to update today, it wouldn't go through. Also when I try to reboot into recovery I'm having issues there, just doesn't want to do it... anyone know why?

Are you pressing all physical buttons then scroll with v down select with v up then press both v buttons at red android screen then select file from SD and apply
https://www.youtube.com/watch?v=6efI1iGAgsU&feature=youtube_gdata_player
Video link to most of process from my YouTube
Sent from my XT907 using xda app-developers app

I missed the step about both v keys at the M, I'm getting it to work now, except I can't find the file. I know its there, can go look at it in the file explorer, but can't find it in recovery.

Did you move it to your SD card it goes to your internal first not external which is where it has to be also did you rename to update.zip?
Sent from my XT907 using xda app-developers app

I apologize if this is something obvious, but when I try and run this through rsdlite (5.7 and 5.9) on my retail M running the JB leak, it immediately fails and says "Failed flashing process. Unknown fastboot command. (getvar)".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Got it, didn't know it wasn't downloaded to my external memory. Its all good now, thanks!

Got it to work by removing the getvar line in the xml (per mattlgroff, no way I would've tried that myself) - works perfectly from the JB leak, thanks again for this!

Just to be clear, is the the stock ROM that came with the RAZR M? That way people could try out the JB leak, and then use this to revert back. Since there isn't a way to install CWM and do a backup.

FAUguy said:
Just to be clear, is the the stock ROM that came with the RAZR M? That way people could try out the JB leak, and then use this to revert back. Since there isn't a way to install CWM and do a backup.
Click to expand...
Click to collapse
Correct, on the current leak anyway. Obviously if you have to do this your data will be wiped as well.

jntdroid said:
Correct, on the current leak anyway. Obviously if you have to do this your data will be wiped as well.
Click to expand...
Click to collapse
But the only way you could get it to work was by removing the getvar line in the XML?

FAUguy said:
But the only way you could get it to work was by removing the getvar line in the XML?
Click to expand...
Click to collapse
That's the only way mine would work - rsdlite wouldn't go past that.

Use RSD Lite 6.1.4

When using RSD Light, does the phone have to be in normal "power on" mode, or in a special "download" mode for RSD to install the files?

FAUguy said:
When using RSD Light, does the phone have to be in normal "power on" mode, or in a special "download" mode for RSD to install the files?
Click to expand...
Click to collapse
AP Fastboot - from powered off, hold down volume-up AND volume-down, then while holding those, press and hold the power button until you see a menu pop-up that's simply white text on a black background. Once that comes up, use volume-down to move down to AP Fastboot, and volume-up to select it. Then plug it into your computer, fire up rsdlite (6.1.4! ), open the file linked in the OP, and go!
Sent from my XT907 using Tapatalk 2

Ok, thanks.
I've posted the files and instruction here:
http://www.phonearena.com/news/How-to-restore-your-Motorola-DROID-RAZR-M-back-to-stock_id35580
If anything needs editing, let me know.

FAUguy said:
Ok, thanks.
I've posted the files and instruction here:
http://www.phonearena.com/news/How-to-restore-your-Motorola-DROID-RAZR-M-back-to-stock_id35580
If anything needs editing, let me know.
Click to expand...
Click to collapse
Credits Firmware Team?
Enviado desde mi HTC Sensation XE with Beats Audio Z715e usando Tapatalk 2

help im stuck
ok so i messed with the build.prop and cant get the original one in through adb, i tried flashingjust system img thru fastboot but the file is too big just error after error with cmd prompt...
so i downloaded stock firmware per phonearena link, and i have rsdlite 6.1.4 installed as well as all the latest drivers, it fails on step 1 "gpt_main0.bin" so i removed that line from xml and tried again, it got further but failed at fsg.mbn
i dont know what to do, i figure if all i need is a good build.prop i should have rsd flash just the system.img but that doesnt work either...
i don't know what to do? any suggestions, or ideas?
---------- Post added at 08:11 PM ---------- Previous post was at 07:30 PM ----------
ok i solved it, nevermind

tadgerloks said:
ok so i messed with the build.prop and cant get the original one in through adb, i tried flashingjust system img thru fastboot but the file is too big just error after error with cmd prompt...
so i downloaded stock firmware per phonearena link, and i have rsdlite 6.1.4 installed as well as all the latest drivers, it fails on step 1 "gpt_main0.bin" so i removed that line from xml and tried again, it got further but failed at fsg.mbn
i dont know what to do, i figure if all i need is a good build.prop i should have rsd flash just the system.img but that doesnt work either...
i don't know what to do? any suggestions, or ideas?
---------- Post added at 08:11 PM ---------- Previous post was at 07:30 PM ----------
ok i solved it, nevermind
Click to expand...
Click to collapse
PLEASE post what you did to fix this issue as it may creep up again for someone else. These posts I run into every so often on google asking a problem and then all I see is "fixed it" no solutions posted. =) thanks!

I deleted the bad build.prop from the system, and The recovery-from-boot.p file or something similar in name, they're the only 2 files in /system that aren't folders, after I rebooted into AP Fast boot and through cmd.exe on win7 and typed in "fastboot -w"
Then "fastboot reboot"
Back too fastboot mode, start RSDLite 6.1.4 w/admin privileges, extracted firmware manually, edited XML too remove any line wit "var" or "OEM" in them, as well as the line with "gpt-main0.bin" I pointed RSD too the XML and it flashed flawlessly
Now I'm back on JB Leak and rooted

[GUIDE}How To Flash Stock ROM With RSD Lite

Do it at your own risk and read it carefully!
I combine the guide for ICS and JB flashing.
- Download the latest driver for Windows HERE and for Mac HERE.
- Download RSD Lite HERE.
- Download stock ICS HERE
- Download stock JB HERE
- You need to open the zip of the rom and find xxx.xml. Open it and notice line like . You should remove both lines to avoid error at flashing. Or you can download my modified xml for ICS HERE. For JB HERE. Replace your original xml.
- Install drivers and RSD Lite to your PC.
- Make sure your battery at least 80% before we proceed.
- Turn off your phone and press both volume keys and power on. You'll enter bootmenu options. Choose AP Fastboot by scrolling with volume down and volume up to select.
- Connect your phone to PC and your PC will detect and install the drivers automatically.
- Open RSD Lite and click ... beside filename. Browse to your ROM and double click it. A menu will popup and choose "uncompress and start flashing".
- It will start flashing once it finishes uncompressing.
- Sit down and relax.
If you want to replace stock recovery with CWM,you can do it by replacing THIS over the original one inside the zip. Thanks to skeevy420.
Note : You can't downgrade if you are on JB to ICS via RSD Lite. With an unlocked bootloader,you can do that with fastboot.
Screenshot added to second post. Thanks a lot to devilsking.

Ha ha. Finally U did it . and now I found an useful guide of how to flashing stock firmware :">. But it's better to add screenshots then make ur guide more clear so I will help u to finish it. Anw, Thank you bro
1. After download required files, open stock rom (*.zip) and you need to find the xml file with name of firmware:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. Open that xml file with notepad (I recommend Notepad ++) and delete 2 get var lines then save it:
3. Open the fastboot mode (Turn off your phone and press both volume keys and power on then select by volume +, scroll by vomlume - or )
4. Open RSDlite, select firmware with edited xml and let it decompress then flash.

Nice,bro.. I'll edit my post and insert your pictures when I'm on PC. It will be better with pictures. Thanks,bro..
Sent from my XT897 using Tapatalk 2

huatz84 said:
Nice,bro.. I'll edit my post and insert your pictures when I'm on PC. It will be better with pictures. Thanks,bro..
Sent from my XT897 using Tapatalk 2
Click to expand...
Click to collapse
Just write a note about screenshots in post #2 is ok. No need to re-insert pictures becoz it makes double contents

devilsking said:
Just write a note about screenshots in post #2 is ok. No need to re-insert pictures becoz it makes double contents
Click to expand...
Click to collapse
Added! Thanks,bro..
Sent from my XT897 using Tapatalk 2

To expedite things a bit, you could also add to the OP to change the md5sum of the fastboot's recovery.img and replace stock recovery with Epinter's CWM. Don't have Windows to test so I'm not sure if it'll work, but it should. That way they don't have to "fastboot flash recovery recovery.img" afterwards.
md5sum=0437ea5bba4433c0e8387493afb821cd

skeevy420 said:
To expedite things a bit, you could also add to the OP to change the md5sum of the fastboot's recovery.img and replace stock recovery with Epinter's CWM. Don't have Windows to test so I'm not sure if it'll work, but it should. That way they don't have to "fastboot flash recovery recovery.img" afterwards.
md5sum=0437ea5bba4433c0e8387493afb821cd
Click to expand...
Click to collapse
Thanks,bro.. so after replacing stock recovery.img,we'll end with epinter's cwm instead of stock? This is useful for those who don't want to do fastboot cmd things. I'll add it soon. I'm on my Photon Q right now.
Sent from my XT897 using Tapatalk 2

huatz84 said:
Thanks,bro.. so after replacing stock recovery.img,we'll end with epinter's cwm instead of stock? This is useful for those who don't want to do fastboot cmd things. I'll add it soon. I'm on my Photon Q right now.
Sent from my XT897 using Tapatalk 2
Click to expand...
Click to collapse
Exactly.
That's what I was thinking.

HELLP!!!! pleace
skeevydude said:
Exactly.
That's what I was thinking.
Click to expand...
Click to collapse
Hello friend, I have a At & t AHD MB886 native JB. when I did a factory reset is hung up and when it starts motorola logo appears and then the screen goes black and does nothing enlightened, did hard reset, recovery, all you can do and the machine will not start. What I can do? the tutorial "How To Flash Stock ROM With RSD Lite" work??

fedefenix said:
Hello friend, I have a At & t AHD MB886 native JB. when I did a factory reset is hung up and when it starts motorola logo appears and then the screen goes black and does nothing enlightened, did hard reset, recovery, all you can do and the machine will not start. What I can do? the tutorial "How To Flash Stock ROM With RSD Lite" work??
Click to expand...
Click to collapse
It should.

ok
fedefenix said:
Hello friend, I have a At & t AHD MB886 native JB. when I did a factory reset is hung up and when it starts motorola logo appears and then the screen goes black and does nothing enlightened, did hard reset, recovery, all you can do and the machine will not start. What I can do? the tutorial "How To Flash Stock ROM With RSD Lite" work??
Click to expand...
Click to collapse
achievement and time to install and works well, the only problem is that I connect to the wifi network, I will keep trying

May be a baseband / modem problem follow my tutorial
here.

Couldn't flash stock via fastboot after CM10, this was very helpful. Thank you.

Sticky bit factory_fastboot and flash failure at 17/21 in rsd lite. Any suggestions?
Sent from my MB886 using xda premium

helldogg75 said:
Sticky bit factory_fastboot and flash failure at 17/21 in rsd lite. Any suggestions?
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
Make sure your harddisk has at least 3gb free space. Try reflashing it.

This is nice, thank you.

Works Great For Me
now i have a Motorola Atrix HD with Bootloader unlocked and Recovery but when i try to put a new Rom in the Phone Dont Put the new Rom overwrite the Rom in the AT&T Rom (try with Batakang Rom) if i try with Cyanogen or another dont give Me that Problem ?

Um what?
Sent from my JokerMATRIX HD MAXX

Did you mount /system before flashing Batakang? For roms intended for flashing in SafeStrap, like Batakang, to flash in CWM you must mount /system first.
You know what they say... Once you go Android, you don't go back. Flashaholic for sure.

Hi
Follow the instructions mentioned on this website and your good go ... I bricked mine last night trying to figure out how to switch network bands and used this one to get my device back and going
Hope it helps
"theunlockr.com/2013/03/05/how-to-unroot-the-motorola-atrix-hd/
Sent from my MB886 using xda app-developers app

[Q] Nexus 7 Nakasi factory .img wont flash

Hi guys im new to the nexus 7, i have previously owned a samsung galaxy s wifi 4.0(piece of crap), i had unlocked and rooted my nexus using the nexus root toolkit v1.6.3. Then i flashed francos latest release kernel through the francos kernel app, Next i downloaded the beats+xlouder mod, i attempted to flash it through cwm by installing zip, it seemed to work, booted then said, something about configuring apps and it got stuck on that. I tried rebooting many times but it didnt work. So then i tried to flash a nandroid backup i had made through the toolkit, this failed. Now i have been trying to flash the nakasi factory image through the toolkit, here is the message i get;
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Anyone have any ideas as to whats going on? and how i might get the nexus working again?

Don't use toolkits.
Apparently, your bootloader won't flash correctly. What version is your bootloader now? If you want to flash android 4.2.2, then it should be 4.18.
Check your USB-cable. If possible, use the one that came with the nexus 7. Check your bootloader img-file. Is the md5-sum correct? If uncertain, then redownload the firmware here: https://developers.google.com/android/nexus/images#nakasi
Extract the contents of the firmware file in your folder with adb and fastboot.
Put your nexus 7 in fastboot/bootloader mode (you can do this by pushing all three buttons on the sides simultaniously).
Type (this will erase everything from your device):
: fastboot erase boot
: fastboot erase cache
: fastboot erase recovery
: fastboot erase system
: fastboot erase userdata
If you need to update your bootloader, then type:
: fastboot flash bootloader bootloader-grouper-4.18.img
If you get an error like signature failed, then recheck your USB cable. This should work. If not, then download the android 4.1.2 firmware and skip flashing the bootloader. You can do an OTA update later.
: fastboot reboot-bootloader
Then type:
: fastboot -w update image-nakasi-jdq39.zip

I had a few troubles on my first attempts too... My suggestion is to get Nexus7 Toolbox from the Sticky in the Development section and flash the image you have, that always worked without a hitch for me!
Good luck!

Is it really important to use the USB cable that was delivered with the device? Did not know there's a difference!
Sent from my Xperia Tipo using xda premium

random hero said:
Is it really important to use the USB cable that was delivered with the device? Did not know there's a difference!
Sent from my Xperia Tipo using xda premium
Click to expand...
Click to collapse
Probably not, but I have seen forum posts where people reported different experience with different cables used to flash firmware. I only experience it when charging. My nexus charges faster with the original cable and charger. Also the original cable's small end is slightly longer than the small end on the cable I got with my samsung smartphone. If it makes any difference when flashing? I am not sure, but to rule out bad USB-cables as a reason for firmware not flashing I always use the original cable.

My bootloader versin is 4.18, how exactly do i check md5 sums,?
i have no experience with fast boot and adb, are they pc programs? If so cqn you give me a link to them?
Sorry im sure you guys get sick of idiots like me asking questions all day but i really appreciate the help

If your bootloader version is 4.18, then there is no need to reflash it and you can skip this step. Don't worry about feeling idiotic for asking questions. Up until I first rooted my nexus, I had no idea how everything worked either. I learned everything by myself, but it's not that easy for everyone.
You can find adb and fastboot in the folder platform tools in the official google android SDK. Instead of downloading the entire SDK, you can also just download the latest platform tools online from many file share websites: https://mega.co.nz/#!1c1XjIIC!dTyG200R4V3BPIfrac4xayEttP02f9tYlPkqAlqvTko .
Extract that folder. Go to that folder. Hold shift and click with your right mouse button and select open terminal prompt.
Now you can use fastboot to flash images, recoveries, bootloaders, erase your devices, restore, etc.....

yeah ok, ill try it and fingers crossed that it works

i tried to flash it but it says
error: failed to load 'image-nakasi-jdq39.zip
the file i have is a .tar, would that be the problem?

Yes! We found the problem.
You need to unzip the tar file as well. 7-zip can do this for example.

thanks guys i got it to work, any suggestions for a fast and stable rom?
:laugh:

TheFro74 said:
thanks guys i got it to work, any suggestions for a fast and stable rom?
:laugh:
Click to expand...
Click to collapse
http://www.modaco.com/forum/657-google-asus-nexus-7-nexus7modacocom ... but I would say that wouldn't I, given it's my own ROM of choice.
Leaving aside my own personal preferences, check out these two threads for ideas and recommendations...
http://forum.xda-developers.com/showthread.php?t=2151963
http://forum.xda-developers.com/showthread.php?t=1807811
The question you have to ask yourself is... do you want full-on functionality, with shed-loads of bells and whistles... or a lean, mean, and minimalistic ROM... or, perhaps something inbetween.
The choice, as they say, is yours....
Rgrds,
Ged.

One of the fun things about the nexus 7 is to experience different roms yourself. See what they differ, what they have in common, what you like about them, etc. I liked paranoid android a lot. I found it very creative, but it didn't ran fluent for me. I even tried ubuntu, but that's just not ready for daily use yet. Now I settled for CM 10.1 M3. It's very stable, smooth and provides a better experience than stock, which I was looking for. But it might be too basic for you. Try it out! And make NANDROID BACKUPS before you do!

Thanks guys , my current setup is a cm10.1 snapshot with Franco's kernel.
Sent from my Nexus 7 using xda app-developers app

[Help} Phone won't boot past "Warning Bootloader Unlocked" after restart

I'm having the same issue as in this thread: http://forum.xda-developers.com/showthread.php?t=2417726
But there was no resolution that the OP posted.
I was running the 9/13/13 PacMan rom when I tried to restart because the phone was running slow. When the phone booted back up, it was stuck at the unlocked bootloader message.I could get into CWM, I tried to reflash the rom, and wipe everything but nothing worked. I also tried flashing all 3 of the stock firmwares (found here: sbf.droid-developers.org/dinara/list.php) in RSDLite, but they all fail. I was trying to follow the instructions in post #6 of the other thread, but they weren't making sense to me..... what can I try. Currently I'm just sitting here at the fast boot screen.
Thanks

skatingrocker17 said:
I'm having the same issue as in this thread: http://forum.xda-developers.com/showthread.php?t=2417726
But there was no resolution that the OP posted.
I was running the 9/13/13 PacMan rom when I tried to restart because the phone was running slow. When the phone booted back up, it was stuck at the unlocked bootloader message.I could get into CWM, I tried to reflash the rom, and wipe everything but nothing worked. I also tried flashing all 3 of the stock firmwares (found here: sbf.droid-developers.org/dinara/list.php) in RSDLite, but they all fail. I was trying to follow the instructions in post #6 of the other thread, but they weren't making sense to me..... what can I try. Currently I'm just sitting here at the fast boot screen.
Thanks
Click to expand...
Click to collapse
When you use RSD, why does it fail? If it fails because it can't find the device, go into your device manager(assuming you have windows) and there is going to be a
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(I believe it says Full Android Emulator) right click that one and install the driver by choosing one and use the Motorola ADB driver. Replug the device then try again.
Now, if you are using RSD and the device is showing, is it failing due to the XML files being wrong? Remember you have to delete the GetVar max download size lines, there is two of them, as described here http://forum.xda-developers.com/showthread.php?t=2231249&highlight=rsd

When trying to flash: 7.7.1Q-144_MB886_MR1-22_SIGNED_CFC.xml
RSD Lite is giving the error: "Failed flashing process. Unknown fastboot command. (getvar)"
7.7.1Q-115_MB886_FFW-14_SIGNED_CFC.xml
Error: "Failed flashing process. 1/23 flash partition "gpt_main0.bin" ->Phone returned FAIL."
MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml
"Failed flashing process. Unknown fastboot command. (getvar)"
In Device Manager it says ADB Interface -> Mot Single ADB Interface.
I have use ADB commands with this computer to the ATRIX HD before so it should work.
In fast boot, I've noticed it says
"Fastboot reason: Flash Failure
usb connected
downgraded security version
update gpt_main version failed
preflash validation failed for GPT"
UPDATE:
I have removed the "<step operation="getvar" var="max-download-size" />" lines from the .XMF files now I get the "Failed flashing process. 1/23 flash partition "gpt_main0.bin" ->Phone returned FAIL." on all the files.

Make sure the files are put on desktop and not a folder and try again going to stock
Sent from my Atrix HD using ProBAM rom and XDA 4 Premium

SVLAN said:
Make sure the files are put on desktop and not a folder and try again going to stock
Sent from my Atrix HD using ProBAM rom and XDA 4 Premium
Click to expand...
Click to collapse
That didn't seem to help. Before I just had them on the root of the D drive but I am getting the same errors from the desktop. Not sure if it matters, but I'm running RSD Lite 6.1.5.
Update: Tried 6.1.4... no luck.

Maybe running the rsdlite as admin?
Open a new Fastboot without usb connection to PC then connect and open rsdlite again and try. I had this problem before and playing with it i manage to flash stock. I forgot how exactly I did though. Just keep trying. I know one of my issues was to put the att stock rom on desktop
Sent from my Atrix HD using ProBAM rom and XDA 4 Premium

SVLAN said:
Maybe running the rsdlite as admin?
Open a new Fastboot without usb connection to PC then connect and open rsdlite again and try. I had this problem before and playing with it i manage to flash stock. I forgot how exactly I did though. Just keep trying. I know one of my issues was to put the att stock rom on desktop
Sent from my Atrix HD using ProBAM rom and XDA 4 Premium
Click to expand...
Click to collapse
Just tried that, I am now using a real Motorola USB cable too.
If I remove the "<step operation="flash" partition="partition" filename="gpt_main0.bin" MD5="900113B868E61E8FC4E59F72C0B67193" />" line from all the files, I get an error that says "Failed flashing process. 1/22 flash sbl1 "sbl1.mbn" -> USB error occurred while reading/writing." Otherwise, I get the error "Failed flashing process. 1/23 flash partition "gpt_main0.bin" -> USB error occurred while reading/writing."
I'm not sure what I'm doing wrong here. This isn't my first Motorola phone, I've used RSD Lite before in the past as well as ODIN for Samsung phones and have never had any issues so difficult to solve. I'm not even sure what file I should be flashing. I came from the latest 4.1.1 then flashed 4.3 PacMan rom.

I tried another computer and getting the same errors in RSD Lite. In Myth Tools, it says it's flashing the firmware for about 15 minutes but when it reboots, it seems to just go right back into fastboot.
I tried to manually push something using fastboot and this is what I get:
D:\Parker\Desktop\Myth Tools - AHD>fastboot flash sbl1 sbl1.mbn
sending 'sbl1' (99 KB)...
OKAY [ 0.022s]
writing 'sbl1'...
Battery Low!!
FAILED (remote failure)
finished. total time: 0.283s
D:\Parker\Desktop\Myth Tools - AHD>
Click to expand...
Click to collapse
Is it failing BECAUSE the battery is low? It doesn't seem to be charging.
I bought the Motorola Factory Adapter from Team Black Hat. I saw on write-up on droid life on how to create one but I really don't have the time to do it.

Buying the adapter solved the problem.

Were you able to flash other ROMs successfully & stably after that? I've been in the same boat & can't get past a reboot after flashing a custom ROM.

bsmitty said:
Were you able to flash other ROMs successfully & stably after that? I've been in the same boat & can't get past a reboot after flashing a custom ROM.
Click to expand...
Click to collapse
Yes I was. I installed a different ROM but... I woke up after leaving it on the charger all night a few days ago and the phone was off. Getting the unlocked bootloader message again... the only way to get around it seems to be reflashing. It's really annoying.

skatingrocker17 said:
Yes I was. I installed a different ROM but... I woke up after leaving it on the charger all night a few days ago and the phone was off. Getting the unlocked bootloader message again... the only way to get around it seems to be reflashing. It's really annoying.
Click to expand...
Click to collapse
What was your previous stock fastboot used and what rom are you trying to flash? I ask this because our development is based off of 4.1.2 RAZR HD stock and I've noticed 4.1.1 only flashers here sometimes have issues. Since the unlock, my stock changed to 4.1.2 Mex Retail (manually flashed everything via fastboot) and I've only been stuck on the bootloader screen once (had to do the sticky bit fix ).
Also, if you're an ATT user, the Mex Retail radio will give you a better signal and I can say that with 100% confidence. My Dad and I both have Atrix HD's, his runs stock 4.1.1 unrooted and mine running anything with Mex Retail radio, I've had 2 bars of service in known dead zones and my Dad had no service less than a foot away -- and that's happened in multiple dead zone/bad signal areas.

How do I go about flashing just the radio and staying on pac? @skeevydude
Sent from my PACMAN MATRIX HD MAXX

I think this method will work to flash a new radio without affecting the rom. I installed the Mexico Retail radio onto Holoblur without affecting Holoblur at all.
Assuming you have a Windows machine:
1) install the adb/fastboot files to a single directory on my computer;
2) place the NON-HLOS.bin file you got from the desired rom in the adb/fastboot directory from step 1;
3) open a command prompt window as an administrator;
4) install the Motorola USB drivers and connect my booted phone with USB debugging enabled;
5) from the command line, type "adb reboot bootloader" and press the enter key to get my phone into AP Fastboot Flash mode;
6) from the command line, type "fastboot flash modem NON-HLOS.bin" and press enter; and
7) reboot the phone and check to made sure the baseband is the one you wanted.

audit13 said:
I think this method will work to flash a new radio without affecting the rom. I installed the Mexico Retail radio onto Holoblur without affecting Holoblur at all.
Assuming you have a Windows machine:
1) install the adb/fastboot files to a single directory on my computer;
2) place the NON-HLOS.bin file you got from the desired rom in the adb/fastboot directory from step 1;
3) open a command prompt window as an administrator;
4) install the Motorola USB drivers and connect my booted phone with USB debugging enabled;
5) from the command line, type "adb reboot bootloader" and press the enter key to get my phone into AP Fastboot Flash mode;
6) from the command line, type "fastboot flash modem NON-HLOS.bin" and press enter; and
7) reboot the phone and check to made sure the baseband is the one you wanted.
Click to expand...
Click to collapse
Ya forgot one step
0) download snapdragon-fastboots.zip from Batakang and use that everywhere a fastboot command is used
/can also install it with the Android terminal emulator and a dd....
//su
///dd if=/sdcard/NON-HLOS.bin of=/dev/block/mmcblk0p1

skeevydude said:
Ya forgot one step
0) download snapdragon-fastboots.zip from Batakang and use that everywhere a fastboot command is used
/can also install it with the Android terminal emulator and a dd....
//su
///dd if=/sdcard/NON-HLOS.bin of=/dev/block/mmcblk0p1
Click to expand...
Click to collapse
I just used the adb/fastboot included with Myth Tools. Not sure if those files will work for everyone though. I'm not very good at using Android terminal so I tend to stick with doing things from a Windows command prompt

audit13 said:
I just used the adb/fastboot included with Myth Tools. Not sure if those files will work for everyone though. I'm not very good at using Android terminal so I tend to stick with doing things from a Windows command prompt
Click to expand...
Click to collapse
Myth comes with the correct files. Very important to specify the correct fastboot because the stock sdk fastboot doesn't flash our images correctly and has led to a lot of confusion in the past.

skeevydude said:
Myth comes with the correct files. Very important to specify the correct fastboot because the stock sdk fastboot doesn't flash our images correctly and has led to a lot of confusion in the past.
Click to expand...
Click to collapse
Good advice for AHD owners to follow. Thanks.

skatingrocker17 said:
When trying to flash: 7.7.1Q-144_MB886_MR1-22_SIGNED_CFC.xml
RSD Lite is giving the error: "Failed flashing process. Unknown fastboot command. (getvar)"
7.7.1Q-115_MB886_FFW-14_SIGNED_CFC.xml
Error: "Failed flashing process. 1/23 flash partition "gpt_main0.bin" ->Phone returned FAIL."
MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml
"Failed flashing process. Unknown fastboot command. (getvar)"
In Device Manager it says ADB Interface -> Mot Single ADB Interface.
I have use ADB commands with this computer to the ATRIX HD before so it should work.
In fast boot, I've noticed it says
"Fastboot reason: Flash Failure
usb connected
downgraded security version
update gpt_main version failed
preflash validation failed for GPT"
UPDATE:
I have removed the "<step operation="getvar" var="max-download-size" />" lines from the .XMF files now I get the "Failed flashing process. 1/23 flash partition "gpt_main0.bin" ->Phone returned FAIL." on all the files.
Click to expand...
Click to collapse
Old post, but still relevant issue. Hope this helps, anyone else getting these errors.
After unlocking bootloader and having flashed MX retail. When using RSDlite I had to remove the "getvar" lines. I've tried to flash back to ATT stock, but can not get past "gpt_main0.bin".
RSDlite can and will finish flash MX retail and Bell stock after editing out "getvar".

clockcycle said:
Old post, but still relevant issue. Hope this helps, anyone else getting these errors.
After unlocking bootloader and having flashed MX retail. When using RSDlite I had to remove the "getvar" lines. I've tried to flash back to ATT stock, but can not get past "gpt_main0.bin".
RSDlite can and will finish flash MX retail and Bell stock after editing out "getvar".
Click to expand...
Click to collapse
Disclaimer: Even though this worked for me I am not responsible if you brick your phone, I am simply sharing my experience
Okay, this is not for the faint of heart and is going to sound a little backward but it just worked for me an hour ago. RSD no longer recognizes my phone in fastboot mode even though it did two weeks ago. Myth Tools however does recognize my phone, it just won't complete the whole flashing process without "intervention".
btw I am running Windows 8.1 Pro 64bit, and nothing has changed on that.
When using fastboot (mfastboot) to flash manually through the command prompt I get the same error when flashing "gpt_main0.bin" and a few others. Back to Myth Tools,, I was having problems even starting it until I just double clicked on flashing.bat or main.bat instead of running it as administrator. After all I AM the admin of my PC. Then, it worked perfect...until flashing "tz.mbn", it sent it fine, but froze up while writing the file. I thought mmm...it shouldn't take that long to write such a small file, and writing happens on the phone side (I believe) so I unplugged the USB while leaving the Myth Tools window open, which disconnected the phone obviously. I plugged it back in and Myth continued from where it left off, with a failure where I unplugged it obviously. It didn't actually fail though.
(Note: I did this a few weeks ago when I lost my radios and manually flashed "NON-HLOS.bin", which froze, but I followed the same procedure and it successfully flashed it)
Anyway, it got to the last system.img chunk (it writes it in small chunks of 30mb and the last one is smaller, that's how I knew it was the last one) it froze again. I let it sit for about 5mins just to make sure it was written to the phone then repeated the sequence of unplugging and replugging the USB and bang, once again it continued right where it left off. one or two more freezes and voila...it rebooted right back to stock. Well, I had to reflash my radio again, but that was easy.
FYI: My xml file has the two "getvar" lines removes due to my earlier attempts with RSD. Any questions don't hesitate to ask.