No CWM for me? Primo not going into CWM recovery any way I try
So I unlocked the prime after realizing root was not the only thing I needed to start flashing ROMs.. TRUE
I rooted using Sparky's method, so easy too. I also tried to root with viper mod one time when apparently Sparkys wasnt working again after I did something like un-root for fun. But Vipermod failed due to drivers that weren't installed and still haven't, reason: could not figure out how or what part was the driver to be installed nothing i clicked on (in XP) worked to download the drivers. however XP does recognize the prime after Windows Media Player update 11 . it said flash complete or successful . I've flashed CWM from the app itself but the only real function I have from it is fixing permissions...
So should someone like me who just reads downloads and flashes (like a madman flasher) to just wait for a newer version that is fully functional so I dont mess things up and need to learn hours of great knowledge to unbrick the TFP/???
I've read that its not really working all the way is this true???
and another ?Q: I want my web to be speedy like Speedy Gonzales so what do I delete from it and what is the best web browser for speed surfing... this prime was crawling around untill I deleted some things that were uselessly running it seems to have worked a bit but not enough a delete list would be rad. Also one other question was it my order of operations which led to a faulty CWM? though I ve reflashed it several times to no better result.. And also if you are still reading (and thank you very much if you are) I dont know how to manually give CWM a go or how to manually get into recovery--- volume up and down plus power seems to soft brick the Prime untill I hold down the power button for a while untill it vibrates for a second then release and push it again to turn it on....and I held power plus volume down but such small print showed up on the upper left corner that i couldn't really know what to do... I also saw the symbols one was a USB symbol,Q: What is this function? WHat would happen should I push the USB symbol ???... ALso can I get updates from Asus after the unlocker app has been used EDIT: DON"T need them however I will find out how to turn these FOTAs off . And Q: does anybody know how to keep the Logitech keyboard connected it times out so when you go back for it it can take a good thirty seconds recovering from its nap... any fix? thanks alot I cant wait to start flashing better ROMs than stock, mine is fairly buggy
___________________________________
Mytouch 3g Cyanogen Mod
Galaxy S 4G Lightning Zapped! Valhalla Black
Galaxy S2 T989 Darkside Kernel ROM:Juggernaut 5.0
AND A VIRGIN PRIME TO FLASH BANG
___________________________________
It is hard to tell if you tried to go into CWM correctly...here is how:
With the Prime OFF, hold the vol down button and the power button until the white lettering appears (you seemed to do that). Then, you have a few seconds to hit the vol up button. (If you wait too long, it won't work.) You should go into recovery at that point -- CWM version 5.8.2.0.
I did the first version of the recovery install manually, like you. But, honestlly, just download ROM Manager from the Market and let it install the latest Transformer Prime CWM for you. If it cannot do it, you have a problem.
If ROM Manager cannot do it, you are probably not actually unlocked. Do you remember giving your rights away to your warranty? If not, you did not unlock and you need to run the unlock .apk. Most of the guys with CWM problems did not unlock their devices correctly.
(P.S.) Personally, if my Prime had been too buggy, I would not have unlocked it. I would have RMA'd it!
Thanks
tedr108 said:
It is hard to tell if you tried to go into CWM correctly...here is how:
With the Prime OFF, hold the vol down button and the power button until the white lettering appears (you seemed to do that). Then, you have a few seconds to hit the vol up button. (If you wait too long, it won't work.) You should go into recovery at that point -- CWM version 5.8.2.0.
I did the first version of the recovery install manually, like you. But, honestlly, just download ROM Manager from the Market and let it install the latest Transformer Prime CWM for you. If it cannot do it, you have a problem.
If ROM Manager cannot do it, you are probably not actually unlocked. Do you remember giving your rights away to your warranty? If not, you did not unlock and you need to run the unlock .apk. Most of the guys with CWM problems did not unlock their devices correctly.
(P.S.) Personally, if my Prime had been too buggy, I would not have unlocked it. I would have RMA'd it!
Click to expand...
Click to collapse
Im giving it a go now thanks for the CWM instructions that part is solved however I asked like ten questions though and am thankful for your answers
I just did a backup in CWM thanks a lot I' d hit thank you again but its gone THANKS!!!
*If I helped hit thanks*
___________________________________
Mytouch 3g Cyanogen Mod
Galaxy S 4G Lightning Zapped! Valhalla Black
Galaxy S2 T989 Darkside Kernel ROM:Darkside
AND A VIRGIN PRIME TO FLASH BANG
___________________________________
I had a similar problem. Bought my Prime from Amazon in the USA and it came preloaded with Honeycomb - imagine that!!! Anyways I struggled as a result to flash a recovery...I seemed to get root quite easily using NachoRoot and ViperMod methods but flashing a recovery and trying to boot into recovery had me ending up with an exclamation marked Android on boot! 1 day of persistent trying and searching high and low, and am glad to report I finally have a rooted Prime with working recovery (just about to flash Touch Recovery now and then a custom ROM...) running ICS 4.0.3...
My steps:
Trying to flash a custom recovery on HoneyComb really was the show-stopper here, using NachoRoot, Memphi*, nor ViperMod...it just wouldn't work using ADB, fastboot etc
So after 1 day of trying and almost dreading having to send the device back to the US for a swap out, I decided to focus instead on upgrading my firmware to 9.x.x.15 (just below the .21 version which has no root tool at the moment!)
So downloaded a pre-rooted ICS 9.x.x.15 custom ROM from somewhere (google is your friend here) and then followed this tutorial here: http://forum.xda-developers.com/showthread.php?t=1492887
Once I was on ICS, it was then easy to use ViperMod (excellent tool!) to quickly get rooted and successfully flash CWM
Great work to the devs of the different tools I have come across and used.
great
fyi, you only need root to flash cwm FROM rom manager, otherwise you can use fastboot to flash cwm manually.
Sent from my TF201
Related
O.K. So my baby (HTC Dinc) was lost in a bunch of snow. I was running android 2.2 with scence UI 2.0 and never had any trouble finding new and exciting roms that were just a lot of fun to play with. So after doing little homwork and having the Verizon guy talk up this Samsung I made my next $200 plunge into my new favorite hobby. However I was not aware that this phones hacking community was so... confusing. So heres where im sitting I ran FascinateRoot_v02 which is a 1 click root and boom i get Superuser. Completely psyched to get a rom on that isn't plagued by Verizon advertisements and Bing Bull$#!t, alas i am stuck. rom manager went in and installed ClockworkMod 3.0.0.8 as its recovery. I download the SuperDark1.1-D101 and go to install it through ROM manager and nothing happens. then i realized that i must not have the right recovery. I am lost and hating the frustrations that are fallowing the events that led to me getting this phone. I know the hardware is good and all but Big Red and Bing (WTF is this doing on a google OS Phone) have turned the wonderful SuperAMOLED screen into an eyesore.
Here's what I need.
1.) someone to post what the OTA update did to my phone. (USB not recognized by PC)
2.) Someone to explain in very small words how to ROM this phone with the latest info.
3.) Someone to explain What VOODOO and NoN-VOODOO Kernels are and the benefits of both
4.)How to install the kernels
5.) Anything that i can do to help with 2.2 because running with limited/no flash makes me feel like im playing with an iphone original with a shiny new screen.
I'm very sorry for making a new thread that i am sure has questions that have been asked before on it, but for two days i have been lost on this. Please help a guy out!!!
Droidneedzsence said:
O.K. So my baby (HTC Dinc) was lost in a bunch of snow. I was running android 2.2 with scence UI 2.0 and never had any trouble finding new and exciting roms that were just a lot of fun to play with. So after doing little homwork and having the Verizon guy talk up this Samsung I made my next $200 plunge into my new favorite hobby. However I was not aware that this phones hacking community was so... confusing. So heres where im sitting I ran FascinateRoot_v02 which is a 1 click root and boom i get Superuser. Completely psyched to get a rom on that isn't plagued by Verizon advertisements and Bing Bull$#!t, alas i am stuck. rom manager went in and installed ClockworkMod 3.0.0.8 as its recovery. I download the SuperDark1.1-D101 and go to install it through ROM manager and nothing happens. then i realized that i must not have the right recovery. I am lost and hating the frustrations that are fallowing the events that led to me getting this phone. I know the hardware is good and all but Big Red and Bing (WTF is this doing on a google OS Phone) have turned the wonderful SuperAMOLED screen into an eyesore.
Here's what I need.
1.) someone to post what the OTA update did to my phone. (USB not recognized by PC)
2.) Someone to explain in very small words how to ROM this phone with the latest info.
3.) Someone to explain What VOODOO and NoN-VOODOO Kernels are and the benefits of both
4.)How to install the kernels
5.) Anything that i can do to help with 2.2 because running with limited/no flash makes me feel like im playing with an iphone original with a shiny new screen.
I'm very sorry for making a new thread that i am sure has questions that have been asked before on it, but for two days i have been lost on this. Please help a guy out!!!
Click to expand...
Click to collapse
Your mistake was a simple one, you simply used the wrong Clockwork Recovery, the ORANGE. Most of our ROMS are not compatible with that. You need the RED Clockwork Recovery 2.x.x, if you do some searching it is all over here. Your OTA update I have no clue about because you didn't even mention it in the original post except to ask what it did. If USB isn't recognizing, reinstall the Samsung drivers, and try toggling USB debugging. You are now NON-Voodoo, your file system is stock RFS, which is slow. What Voodoo does is change your filing system to EXT4, which is must faster. This does not mean your phone will be blazing through everything. It simply means that your phone will be much faster at writing data, I have not seen one person disappointed per se in it yet, I personally use it. Overall, it will increase the performance of your phone. Kernels, you flash using the RED Clockwork Recovery, which you will find downloads of and instructions for all over this forum, it is very easy. Once you get the correct Clockwork Recovery this will be easy man, so go get that, and flash a ROM like you normally would. Have any more questions, you can reply, or IM me. EDIT: Also, get a program called Odin, which is all over this forum as well. As you read more and more, and do more things, you will see why it is very useful.
Thanks! 1 problem... I cant set it back using rom manager. How else can you fix/downgrade to 2.x.x. Also the OTA update has my phone hidden on my pc through USB conectivity and I have never used Odin. I really do appreciate the help! I hate trying to learn new setups in 2 days
Sent from my SCH-I500 using the XDA mobile application powered by Tapatalk
Droidneedzsence said:
Thanks! 1 problem... I cant set it back using rom manager. How else can you fix/downgrade to 2.x.x. Also the OTA update has my phone hidden on my pc through USB conectivity and I have never used Odin. I really do appreciate the help! I hate trying to learn new setups in 2 days
Sent from my SCH-I500 using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
Okay, here is Odin, attached at the bottom of my post. I am also including Clockwork Recovery, the one you need, as well as the update.zip. First you need to place Update.zip on your SDCARD. Since your pc won't recognize your phone, you can use the Dropbox program to do this. Update.zip HAS to be on the root of your SDCARD. Now, Odin is the program you want to use to Flash the cwm.tar, okay? And ONLY that .tar. Open Odin and mess with NONE of the settings, NONE. Click the PDA Button, choose cwm.tar and then click on START. Note: In the upper left hand corner, if Odin detects your phone, it will be yellow. And make sure USB debugging is enabled. So, flash cwm.tar to your phone, boot into recovery by holding BOTH of the volume keys while powering up, then in Clockwork Recovery select "Install Update.zip", it will install and you will have the RED Clockwork Recovery. THEN you go flash your ROMS and such, as for your USB problems, could be very simple, just do some Googling. Oh, and in terms of ROMS? I HIGHLY recommend Adrynalyne's SuperClean.
One thing to note since you have been having problems, and because I didn't see it mentioned above.
For odin to work (for odin to see your phone) you need to have it (your phone) in download mode.
This is made possible by pulling the battery, plugging in the phone to your PC via the STOCK usb cable (I have read non OEM cables can cause problems), and holding down the "down" button on the volume rocker while holding the power button. You should boot into download mode. Yellow Triangle as some call it...because of the giant yellow triangle on-screen....
I had a hell of a time figuring this out through the guides but once you figure it out you will have no problems.
gkirby11 said:
One thing to note since you have been having problems, and because I didn't see it mentioned above.
For odin to work (for odin to see your phone) you need to have it (your phone) in download mode.
This is made possible by pulling the battery, plugging in the phone to your PC via the STOCK usb cable (I have read non OEM cables can cause problems), and holding down the "down" button on the volume rocker while holding the power button. You should boot into download mode. Yellow Triangle as some call it...because of the giant yellow triangle on-screen....
I had a hell of a time figuring this out through the guides but once you figure it out you will have no problems.
Click to expand...
Click to collapse
I KNEW I forgot something, thank you for adding that. I have so much going on but did not want to leave the guy hanging I rushed through the explanation.
There were some issues with the "stock" versions of CWM, and our devs have touched it up to work with our phones better. The latest "Orange" version you installed from Rom Manager uses a new method for installing updates/ROMs (Edify script). Almost all of the things available on these forums are still set up for the old method of installing updates/ROMs (Amend script). As a general rule of thumb, we don't update CWM through Rom Manager, and just use versions posted here. There were some compatibility improvements, but they also added Voodoo support and options.
Also, because of not using Rom Manager to update CWM, the "Install from SD Card" option in Rom Manager doesn't work. There's some kind of "*update.zip" in the clockwork folder on your SD card. If you copy the update.zip from the root of your SD card into the correct folder and rename it, the "Install from SD Card" might work. Sorry, I don't use Rom Manager anymore, so I don't have the exact names or folders.
The way a lot of people handle ROM installs is to reboot into recovery (hold volume up and volume down and power while starting up, and release only the power button when "Samsung" appears). Once you install the cwm.tar that Dread This Day posted, this method will take you straight into Clockwork Recovery. You can download ROMs from Rom Manager or directly from these forums.
Just a word of caution on Voodoo. There are some serious problems you can get yourself into if you don't know what you're doing with it. I strongly suggest you thoroughly research exactly what it does, the impacts of installing/using it, and how to properly remove it before you decide to use it.
Thanks for the info and the walkthrough. Gotta love expediant info. Ill be playing with it after I get off work. I have been using the micro usb from my Dinc so ill swap it out and see if it works.
Sent from my SCH-I500 using the XDA mobile application powered by Tapatalk
all i get from that is samsung recovery utils. lookin over the net and tried the whole emulator trick. this phone is aggravating I know its probably just me. So im going to run some tests to find out if i can get into the download mode via an cmd prompt or some such program.
In other news I FOUND MY Dinc! after a weekend of being in the snow a co-worker spoted a lighter and went to get it, at which point he found the phone under it. great news is that my case and screen protector saved it. no water damage, not even a red seal!
Edit:
The program is called terminal emulator not cmd prompt. sorry for the platform crossover.
In emulator
type in #su
agree to superuser
type in #reboot download
and done. i knew that computer class would pay off. lol next step is getting phone recognized by odin. more fun awaits...
abondon ship. htc thunderbolt is out in the next 3 weeks and im gonna be all over it. as my name infers deoid needs sense and samsung... well it has none and oit of the 5 phones ive rooted and romed this is by far the most anoying. ota updates that make a phone unrecognizable via pc and the need to run multiple programs just to get a phone to except root. no froyo in sight and... bing... they ruined a great phone by pretty much leaving it up to our devs to make it worth something. i shall miss my superamoled but not enough to birn an upgrade. thanks for the help, you guys are great, hope to see ya in the htc scene soon.
Sent from my SCH-I500 using the XDA mobile application powered by Tapatalk
In my opinion ROM Manager blows goats your better off downloading from xda and flashing in the orange clockwork
Sent from my SCH-I500 using XDA App
WhiteRocks said:
In my opinion ROM Manager blows goats your better off downloading from xda and flashing in the orange clockwork
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Most of the ROMs for the Fascinate won't work with orange clockworks. You will need the red version.
Sent from my SCH-I500 using XDA App
Sense really blows dude, I would cut my hand off before going back to buggy htc, 2.2 fascinate is way better, but to each his own...
Sent from my SCH-I500 using XDA App
Hello, somewhat of a quick question. AFter having some installation issues I nvflashed(without installing CWM bec. I didnt know til after about it) to 1.2bl 4349 Then of course went to install CWM8-followed same exact steps and link the 1st time which worked. After extract & placing the update.zip & recovery on root, try to boot into Revovery, sticks a 3 birds screen saying "REcovery key detected BOoting recovery kernel image" From there, Im able to power off and back on to OS everytime. Just not able to see any recovery.
Tried, different links, made sure it said sdcard/not sd2 in command folder, and for other small things with no luck. Been reading similar issues, and seems the answer is to NVflash w/ CWM install??? or is there a more simple fix? Any help would be greatly appreciated.
Clockworkmod 0.8 only works on the 1.1 bootloader. If you are trying to upgrade to 1.2, I would suggest you download the NVFlash for 1.2 with CWM installed. You can find it at Good Intention's website:
http://viewsonic-gtablet-for-dummies.webs.com/nvflash.htm.
I did the upgrade this weekend and bricked my tablet until I found that download. It fixed it right up.
ok thanks for that...Just so you know bought the gtab few days ago, came with 1.2 4349 I did not Nvflash, just did the CWM(CWM3028.1.2internal (1).zip) install with no problems. Had some install and roms issues so I did the NVflash 1.2 without CWM with succes to just start fresh, but cant get to recovery.
Just to be clear Im not trying to upgrade 1.2, im currently already at 1.2 4349 and cant get to recovery.(can get into to OS by holding power button from the stuck 3 birds screen)
My question: Is the only way out of this to follow the the link you provided and nvflash w/ cwm??? If even this would work
Please help thank you
Back to CWM Couple more side questions please
Ok pretty sure I got it....
followed the nvflash for dummies and ran the 1.2 with CWM installed and now I can access CWM...no t sure what happened because I ran did this same thing but w/o CWM and worked fine, then tried to install the CWM 1.2 compatible by putting the 2 items on the root but it would just get stuck at 3 birds screen, although I was at least able to still get into OS from there, just not any recovery. Oh well, pretty sure I got.
See i had already had cwm(NON-Nvflash method) and Vegan tab GE 7.0.0 for 1.2bl installed. After fixing some Fc's, manually installing a browser and market since I could not find them anywhere the common market issues by removing the market updater(couldnt find a way to get new market working), and some other similar issues, I was not able to 2 solve 2 main things that had to be resolved:
~While the regular email app push notifications worked fine, the gmail app would not work. I even had to manually go into the app and hit refresh to even receive them Any knowledge with this would be a life saver
~Vegan-tab settings-i would select and it would immediate FC. Each time I would select, it would do it again Couldnt find a way to make it stop so I could access that menu.
-could get into launcher settings but not Vtab settings...shedding any light here would be great...
So this led me to do Nvflash & reflash a custom rom in hopes of things going much smoother. I hope this irons those issues out...
I hope to get some insight on the above post, thanks in advance...
BTW XDA Developers you are AWESOME and save my ass consistently, all of you are great and I thank you!!! I will be hitting that thank you button
Hey guys, sorry that this is my second thread since I registered, and both are help threads, but this website came highly recommended.
Anyway, I bought an Asus TF201 tablet that came rooted, unlocked, and with CM10 loaded on it. I wiped everything I could in the pre-OS Tweaker thingy and installed an official Jellybean ROM on it that I downloaded from Asus's website. The funny thing is that the tablet was in Chinese upon first boot. Another weird thing is that the Tweaker tool that allowed me to install stuff disappeared.
All that's on there is on the screen is, in this order, RCK (which when selected shows an Android figure with his chest opened and an orange triangle w/ an exclamation mark on top), Android (which boots into the JB ROM), a USB sign (which starts a "Starting Fastboot USB download protocol"), and a Wipe Data sign (which I haven't had the balls to select).
There's also this on the top left corner:
Press (Volume Down) to select, (Volume Up) for selection move
Android cardhV-user bootloader (1.00 e) released by "CN_epad-10.4.2.17-20121018" A03
OS will cold boot in 10 seconds if no input is detected
The Vol Down and Vol Up functions are reversed for some reason.
I don't know what was done to the tablet before I bought it, and I don't know what I did when I wiped the data and installed a new ROM onto it. I'm normally decent with following custom ROM installation guides, but this time I honestly don't know what to do. The only problem with the tablet in its current state is that I can't get Play Store on it, and Asus said that because it's rooted/unlocked, they won't support it.
I'm hoping someone can walk me through a step-by-step process and get this tablet back to as close to factory settings as possible, with Play Store installed.
Sorry I'm asking so much, but I have nowhere else to go.
androidbrownie said:
Hey guys, sorry that this is my second thread since I registered, and both are help threads, but this website came highly recommended.
Anyway, I bought an Asus TF201 tablet that came rooted, unlocked, and with CM10 loaded on it. I wiped everything I could in the pre-OS Tweaker thingy and installed an official Jellybean ROM on it that I downloaded from Asus's website. The funny thing is that the tablet was in Chinese upon first boot. Another weird thing is that the Tweaker tool that allowed me to install stuff disappeared.
All that's on there is on the screen is, in this order, RCK (which when selected shows an Android figure with his chest opened and an orange triangle w/ an exclamation mark on top), Android (which boots into the JB ROM), a USB sign (which starts a "Starting Fastboot USB download protocol"), and a Wipe Data sign (which I haven't had the balls to select).
There's also this on the top left corner:
Press (Volume Down) to select, (Volume Up) for selection move
Android cardhV-user bootloader (1.00 e) released by "CN_epad-10.4.2.17-20121018" A03
OS will cold boot in 10 seconds if no input is detected
The Vol Down and Vol Up functions are reversed for some reason.
I don't know what was done to the tablet before I bought it, and I don't know what I did when I wiped the data and installed a new ROM onto it. I'm normally decent with following custom ROM installation guides, but this time I honestly don't know what to do. The only problem with the tablet in its current state is that I can't get Play Store on it, and Asus said that because it's rooted/unlocked, they won't support it.
I'm hoping someone can walk me through a step-by-step process and get this tablet back to as close to factory settings as possible, with Play Store installed.
Sorry I'm asking so much, but I have nowhere else to go.
Click to expand...
Click to collapse
First up you have installed a Chinese rom onto it.
You have lost your recovery because you installed an official rom which overwrote your recovery.
Go to post 2 here http://forum.xda-developers.com/showthread.php?t=1674827 and follow the instructions to install TWRP ( the normal one ). This will give you a recovery back that you can install a rom from.
Then go to post 1 and follow the instructions to install HairyBean 1.51 or if you want install a different Jellybean based rom.
flumpster said:
First up you have installed a Chinese rom onto it.
You have lost your recovery because you installed an official rom which overwrote your recovery.
Go to post 2 here http://forum.xda-developers.com/showthread.php?t=1674827 and follow the instructions to install TWRP ( the normal one ). This will give you a recovery back that you can install a rom from.
Then go to post 1 and follow the instructions to install HairyBean 1.51 or if you want install a different Jellybean based rom.
Click to expand...
Click to collapse
Thanks for the prompt response. I just want to know beforehand whether or not there's anything I need to worry about when reinstalling TWRP to it, because of what has possibly been done to it in the past. Barring the possibility of me messing up, if I follow the directions explicitly, would everything be okay? I wouldn't cause a permanent brick by overwriting any necessary files or anything?
androidbrownie said:
Thanks for the prompt response. I just want to know beforehand whether or not there's anything I need to worry about when reinstalling TWRP to it, because of what has possibly been done to it in the past. Barring the possibility of me messing up, if I follow the directions explicitly, would everything be okay? I wouldn't cause a permanent brick by overwriting any necessary files or anything?
Click to expand...
Click to collapse
The way people normally hard brick is by flashing a version of twrp or cwm not meant for their bootloader (ie. flashing a Jellybean Twrp onto an ICS bootloader.)
I can tell by your numbers you posted that you are on the Jellybean bootloader and if you want to make 100 percent sure look at where the nvidia logo is when you turn it on. If it is down the bottom center it is ICS, If it is bottom right it is Jellybean.
The Twrp I linked you to on that page is for Jellybean only.
The only thing that might stay with you is the chinese bootloader but I don't think that will effect anything in the rom. If you really wanted to get rid of that also, after you flash twrp and have it working you could follow the instructions in that second post for "Upgrade instructions for ICS"
Even tho you are on Jellybean now those instructions just flash a version of the Jellybean bootloader that I took out of the world wide release, but I wouldn't do that unless there is some unforeseen problem with having the chinese bootloader.
Thanks! Tablet is all good to go now.
So a complicated story:
I bought a transformer prime some time ago then rooted it and installed WOOKIE rom (http://forum.xda-developers.com/showthread.php?t=1674827) then it's sat unloved for a few months.
However I've tried to resurrect it for the festive period and am in trouble. (I've been a keen user of the roms on here for many years, with a smart phone for over 10 years, so I'm not completely thick!)
I'm trying to get paranoid android on it;
However, as soon as I go to CWM and try to install the ROM I get a terrible error message, (Will update once I can get it on my screen but it's on 0% charge currently) but can roll back to install a backup, so that's not the end of the world.
So my issue is how do I get from what I have to where I want to go to?
I think the solution is as follows:
a) I need to get Clockwork ROM working well first. Any ideas?
b) I need to downgrade the ROM to something, But I'm unsure what
c) If a and b are in place, I think I can do the rest.
Please help me! All this talk of downgrading roms has confused me.
1. Let go of CWM. No one uses it anymore. Download TWRP here: http://teamw.in/project/twrp2 It will probably fix your errors and it has a lot more features than CWM, is more polished etc.
2. Without NVFlash you can't downgrade. Here is guide how to do it: https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/ If you don't want to downgrade I recommend you to install CMB rom http://forum.xda-developers.com/showthread.php?t=2501812 It's Android 4.3.1, everything works and is probably fastest ROM that we can get on our primes.
Thank a bunch zdenko1.
I'm on the case, however I left my laptop entirely flat overnight, so it's upto 0% and 3% charged. And it's Christmas eve!
It's really good to have someone help me out with a bit of detail - so thanks for this.
If I don't post, assume it works, and here's to a peaceful Christmas break to you all
Now I think I have cooked my goose!
I was unable to get anywhere with this,
So with an air of confidence I ran a program (again the name escapes me) which lets you return your computer back to stock, from which one is able to get it working and you're back to square 1.
Great I thought and as ususal I throw my self both feet in.
It formats fine etc until it asks me to get the original update ROM/blob I think -
which I didn't have, so hen tried to download it and couldn't find it.
So now I think it really is screwed
Nothing formatted, I can't enter recovery mode and things are looking bad.
Does ODIN work/provide an answer? If so please help!
Of course I realise that ODIN is Samsung own!
So I think I need a ROM/BLOB that restores me to a working copy via bootloader?
Is that on the right line?
Just seeing if I have to give this up as lost and sell as broken or can it be resurrected?
Sent from my SM-N9005 using XDA Premium 4 mobile app
DO NOT INSTALL ANY OTHER RECOVERY WHILE USING THE NEW 4.2.1 BOOTLOADER, THEY ARE NOT COMPATIBLE AT THE MOMENT, THE ONE BUILT IN IS MODDED. USE THE DOWNGRADE ZIP TO TAKE YOU BACK TO 4.1.1 BOOTLOADER AND RECOVERY IF YOU NEED IT.
Click to expand...
Click to collapse
Using the link you provided in the OP, scroll down until you see the downgrade hairybean 4.1.1 bootloader and recovery. That should get you to a point of being able to flash a new rom.
Hey good people, after an entire day of trying to tinker with my phone, I soft bricked it.
It started because I wanted a theme, that required CM. So I've browsed a lot of threads and tried some things, and a couple of restarts and factory resets later, it went downhill.
So, P760 20i, running stock 4.1.2, after the last factory reset, I rooted it using this tutorial. I did that in order to install this CWM, to further install CM 10.1, the one I needed. After I did all that and finally booted up in recovery mode, I wiped user data as per instructions in the last link, and when trying to install the ROM, an error felt the need to interfere with my plans. So that's how I ended up with a phone that, if I don't take 3 more pills now, I'm gonna give to the dog to chew on.
It powers on, passes the LG logo, after the screen goes white and it says Under Coding...and the only option is a button to Reset Phone (it's basically a restart phone). A pop-up immediatly appears, saying that com.android.phone has stopped. After I click OK on that it asks for my SIM PIN, it accepts it, and briefly shows a weird, low-res old-looking Android lock screen and then back to the blank screen with another pop-up, asking me about Mobile Networks. That's about all the interaction there is. Click Home button does nothing, clicking Back button just swipes the screen back on the screen, and Menu does nothing. Rebooting from that button is again useless.
That CWM is still there, I can access boot in recovery mode, but to no avail. I've wiped cache, wiped Dalvik Cache, rebooted and nothing. I've tried hard reset with vol down+home then power for 3 secs, release power but still hold down vol down+home until the friendly robot appears, but the result is the same, nothing happens.
During the day I went through more methods, I had a lot of trouble with fastboot which I couldn't get to work.
My question is, based on what I told you, can you instruct me in the right direction ? Also, now that this happened and if it's possible to fix it, could it be fixed with CM installed automatically, or will it be a stock reset and then again back to the drawing board ?
If you need any more details, I'll try to provide, I didn't do much after the last factory reset except for what you see here.
@nerazull Welcome to the forums.
I guess first things first.... With this device you cannot flash any custom roms without unlocking the bootloader first. You cannot flash any custom roms with this version of CWM recovery either and there is no work around for the bootloader such as loki.
When you installed CWM did you make a nandroid backup? I hope so.... this is always, always the first thing you do before making any changes to the system.
If you did then just boot into CWM and restore your nandroid backup and that should resolve your issue.
If you didn't perform a nandroid backup then you can try and flash one for your specific device (p760 jb) from cmahendra's nandroid thread here - http://forum.xda-developers.com/showthread.php?t=2136204
If the nandroid backup doesn't work then you'll have to follow cmahenda's unbrick guide by either using the offline or online flash here - http://forum.xda-developers.com/showthread.php?t=2085344
@xdrc45 Well, I didn't perform any kind of backup, I usually don't (call me an optimist ...I'm actually sad now )
I woke up earlier and started reading the second topic you posted. I'm thinking about trying that and not the first one, since I see the first one MAY have some personal data, I would prefer a stock option.
The question is, does it matter that it was 20i before, must I find a 20i now, or can I take any other one ? Or any other one respecting country/provider ?
Also, the first one says that device must be rooted. Is it still rooted now, with the method I used and after the incident ?
I also tried a couple of ways to unlock the bootloader yesterday, best result I got was a phone restart but nothing different. I also couldn't find a way to tell if the bootloader was unlocked or not.
PS: Thanks for the welcome
The nandroid backups are clean as in stock, rooted and all personal information is removed.
Personally i would try the nandroid backup firsr as that would be the fastest way to restore your device. Take a total of 5 min to try and yes the device should still be rooted.
My L9 had the same problem after I installed the L9 Recovery, I booted into CWM and made a backup and then when I rebooted to the OS I got the error Encrypting - Reset Phone. Booted back to CWM, restored my backup and everything was fine... turned out to be a problem with BusyBox.
For the kdz you only need one that is for your model# and that is the same version of OS that came installed on the device (ics or jb) for the offline flash.
When you successfully unlock the bootloader you will be taken to a verification screen to actually unlock it. Its a huge pain to achieve. What you can do one you restore the device and make a nandroid backup is
1. Install a launcher lile Apex or Nova
2. Install xposed framework
3. Inatall gravity box xposed module
4. Install xthemes xposed module
All the above allow you to make custom changes from the status bar to kk themes
Ok, I will take your advice and try with the backup first.
And btw, that's the same error I get, I said "Under Coding" because that's the word-by-word translation from my language, didn't think of "Encrypting"
In regards to the theme part, that's what I originally did. I found the same version of the theme I wanted as an XTHEME. I followed the instructions of the developer on the play store. I rooted using the same method I mentioned in OP, got the XPOSED framework, got XTHEMES Engine, got the theme, but it wasn't working as intended. The theme only changed a couple of icons and the battery icon, it was like 20% of what the screenshots on the play store were showing. It also had something resembling 256 colors in the drop-down menu.The comments and rating of the theme made me think that the problem was on my end.
I found the same theme that had another application method, and required one of these: CM10.1, CM10, CM9 ,AOKP and Paranoid Android, so I decided to try this one with CM10.1, maybe it wouldn't glitch.
Sadly, there were no reviews of the theme for my device, so I couldn't tell if it was a problem with this specific device+that theme.
I can't post outside links due to being new on the forums, but the themes I'm talking about can be found in the Play Store, search term "Deus Ex Android Blue", the first two should be Custom ROM one and XTHEME one. Maybe you have some insight.
PS: I see that you also have this device, albeit 769, and it's the only one with stock ROM on it. I'm not a very experienced user, should I still pursue bootload unlock+custom ROM ? Is it too much of a hassle ? I'd like to do it and not just for the theme (it's the main reason though), if I fix the current problem.
I found 2 methods that used adb/fastboot for unlocking, got Android SDK, adb worked fine but I couldn't do anything about fastboot. I also tried that method (I think "Lelus"), where you had to remove battery, plug in phone like that, "catch" the device and manually install it's driver, etc, but I didn't fully understand what to do there. I only did the first part. There was another link to a tutorial about this method, spanning 3-4 methods, and I saw it's pretty random, and my USB cable is also not very reliable, if I move it by just a bit it may interrupt the connection.
LE: I'm sorry I can't quote all the methods I tried yesterday so you can better respond to me, but I can't even remember all...at one time I had 20+ tabs on the subject, bookmarked a few, tried some, ran into scam websites claiming they had a good method, etc.
And one last thing (sorry for this wall of text reply ), you said this CWM I got can't install Custom ROMs, but can it flash the backup I need ?
@nerazull
See the thing is that using something like xposed framework modules, is that it literally makes changes to the framework and the phone just might not like one of those changes. Sometimes it won't apply all the way across the system and you may only end up with only 20% of the theme working because some of the themes were originally cm10+ themes ported to xposed and may have been developed for a specific device and isn't a 100% compatible or a bad download. Usually if it causes any problems you can just uninstall the module and reboot and everythings fine, if not that's where a backup comes in handy.
I haven't tried to unlocked mine yet, just because I really haven't had the time to spend a day flashing kdz and dealing with the inverted touch screen. I plan on it one of these days, I've already downloaded everything for the device to do it and even have fastboot already set up just in case. So yes you could say it is a pain to unlock the bootloader, but I'm pretty sure more people have been more successful at unlocking on the p760 than on other variants.
Fastboot is actually pretty easy to set up. Open device manager and open lelus fastboot script, minimize the fastboot script windows so you can see them both fully open on the screen. Turn off the device and remove the battery and keep it screen down on a flat surface, plug your USB cable into your PC not into the device yet - select #1 for fastboot - push any key to continue - quickly plug in the USB cable into the device and and put the battery back in - on device manager you will see "unknown device" pop up and right click on it quickly and select update driver - select manually install the driver - then navigate to where you have the fastboot diver folder and click on "usb _drv_windows" and install - once that's done repeat the process again to install the drivers again.
Yes that cwm version will flash the nandroid backup and mod zips.
One other thing you can try is apex launcher, that's what I'm using. With this you can change a lot of the launcher settings, change and edit the size and image for icons and folders to adding themes, I'm using kitkat HD multi launcher theme through apex and its really nice and clean.
I haven't tried it yet but you can also try themer beta
@xdrc45 Well, I managed to install a backup from your first suggested method and it worked fine. I also tried Nova Launcher for a bit, bit I just got my mind set up on that theme and it's not going away I've also managed to install the fastboot drivers using the Lelus method (don't know why, but your instructions here made much more sense to me then the other 2 I found )
I decided I still want to pursue unlocking the bootloader and installing CM 10.1, I really want to check it out.
Will this BL unlocking method work for me ? I couldn't find any mention of 20i in the thread. And if yes, can that CWM flash a custom ROM, unlike my current one ?
And of course, thanks for your help so far. Really appreciate it.
@nerazull Hey you're welcome.... glad I could be of help.
I don't think v20i is unlockable, you could try and issue the unlock command but I'm pretty sure you will have to flash to a European open kdz like v20b and then follow the tutorial and yes that CWM will work.
You could also use markolino631 Tool box to try and unlock the bootloader. It issues the unlock command and can flash CWM for you easily ... There's a CWM for cm10 and the new version has one for cm11.
http://forum.xda-developers.com/showthread.php?t=2190326
I'm surprised you're going for cm10.1 instead of cm11
@xdrc45 Well, I did try to unlock 20i with the method I mentioned but it didn't work, I decided to flash v20b europe open. I flashed v20b Europe Open (just got the kdz from there, didn't follow those steps, didn't go back to ICS) using offline method (had to hard reset after because I was stuck in a bootloop, it worked fine after). I've got the fastboot drivers installed like I said before, I've checked and they're installed correctly. I've also installed/uninstalled the LG drivers twice, once offline to make sure Windows doesn't search for updates, and I still can't unlock bootloader. I've tried both unlocking methods aforementioned and the phone just reboots normally.
I've made these screenshots of what my Device Manager looks like, just for the sake of being thorough.
In phone, Software Version now says P76020b. Could the problem be here, shouldn't it say EUR-something ?
And I'm going for CM 10.1 for that theme, if it works and I like it I'll make a backup and get CM11 and see if they're compatible or not and move on from there That is, if I can get this bl unlocked.
LE: In the [2in1GUIDE] there's this post that mentions BusyBox. My device is not rooted after the kdz flash and obviously I don't have BusyBox. But that wouldn't make sense since it's not a pre-requisite in the tutorial and the tutorial is also meant to root.
There's also this...and this confuses me even further + other random occurrences.
Is it safe to assume that I should start experimenting ?
Yeah these L9's can be a pain in the @ss, but the nice thing is you can recover it from almost anything.
Just keep trying and don't give up on it. I've seen where some people have tried multiple times to unlock, like 20 times without success and then they try again and boom, unlock success. Make sure you have and are using the phones service and wifi. Make some calls and watch some videos or a movie on it.... You need to receive the token, this is the whole reason for waiting an hour before issuing the unlock command, but it may take longer than an hour or two to receive it, like some waited 10 hours and then the unlock worked.
Unfortunately there is no one set way to unlock and everyone has had different experiences and tried different techniques to get it to work. All you can do is, as you said "Experiment" and exhaust all options.