If you want a custom recovery and rom and you just unlocked your bootloader go here:
http://androidhosting.org/Devs/Dhacker29/msm8960/
Download and Flash:
XT901-XT907-TWRP-2.6.3.0-recovery.img
and
cm-11-20140615-UNOFFICIAL-RAZR-HD_M-KITKAT-TEST
and enjoy.
--
ERK
Any way to flash the recovery without a PC?
Sent from my XT907 using XDA Free mobile app
ezknives said:
Any way to flash the recovery without a PC?
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
or
https://play.google.com/store/apps/details?id=com.cgollner.flashify
As always thank you kindly ATTACK...
Sent from my XT907 using XDA Free mobile app
Wich one of those did you use?
And did it work? Can we use rom manager?
Sent from my XT907 using XDA Free mobile app
The first one with twrp 2.7... Worked fine for me...
Sent from my XT907 using XDA Free mobile app
I can't seem to reboot into recovery correctly. Every attempt just lands me back in the stock firmware. Rebooting from there to recovery via adb just gives me the Motorola warning.
Strife89 said:
I can't seem to reboot into recovery correctly. Every attempt just lands me back in the stock firmware. Rebooting from there to recovery via adb just gives me the Motorola warning.
Click to expand...
Click to collapse
This is what I use
https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot
ATTACK said:
This is what I use
https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot
Click to expand...
Click to collapse
No dice. Rebooting to recovery even with that just leaves me staring at the boot image.
EDIT: I remember reading that those who took the KitKat OTA got a different boot image that makes going back to Jellybean difficult, if not impossible. Could that have anything to do with this?
Strife89 said:
No dice. Rebooting to recovery even with that just leaves me staring at the boot image.
EDIT: I remember reading that those who took the KitKat OTA got a different boot image that makes going back to Jellybean difficult, if not impossible. Could that have anything to do with this?
Click to expand...
Click to collapse
Which recovery are you flashing? It should read TWRP2710-RAZR_M-KITKAT.img.
ATTACK said:
Which recovery are you flashing? It should read TWRP2710-RAZR_M-KITKAT.img.
Click to expand...
Click to collapse
Bah, pay me no mind. I was trying to flash a CWM recovery because that's what I'm familiar with. I tried the one you just named and it works fine.
Sorry about that!
Just an FYI I couldn't get rashr to even look for the file so I tried flashify and it installed recovery with ease.
Thanks for the links attack. I don't like to try these flashing apks without a recommendation.
Sent from my XT907 using XDA Free mobile app
Strife89 said:
I can't seem to reboot into recovery correctly. Every attempt just lands me back in the stock firmware. Rebooting from there to recovery via adb just gives me the Motorola warning.
Click to expand...
Click to collapse
Are you Fastboot flashing?
Guys KEEP IN MIND:
These are not officials, these are fairly beta builds. You will get errors, I was hoping this would reach some crack-flashers.
That's basically who this is for.
ericerk said:
Guys KEEP IN MIND:
These are not officials, these are fairly beta builds. You will get errors, I was hoping this would reach some crack-flashers.
That's basically who this is for.
Click to expand...
Click to collapse
How can we get onto official CM then?
I know it has something to do with the kernel. We can't downgrade the kernel to the one CM is using? Or we have to wait until CM move up to kernel 3.4?
gtmaster303 said:
How can we get onto official CM then?
I know it has something to do with the kernel. We can't downgrade the kernel to the one CM is using? Or we have to wait until CM move up to kernel 3.4?
Click to expand...
Click to collapse
The latest Nightly is from February, which is 4.4.2.
Honestly keep checking that website, and check XDA.
Since the bootloader has been unlocked there should be a lot of movement / action in the dev section.
I would honestly not flash anything older, I mean feel free to mess around w/ kernel that are newer than 4.4.2 on CM.
I can't promise anything if you're on stock. I hope that helped at least a bit.
Didn't think this deserved its own thread, but could someone on 4.4.2 upload their systemui.apk real quick?
Sent from my One using XDA Premium 4 mobile app
Leraeniesh said:
Didn't think this deserved its own thread, but could someone on 4.4.2 upload their systemui.apk real quick?
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Odexed or Deodexed?
Here's a Deodexed SystemUI
I'm unable to boot official CM 11, yes i flashed it with TWRP2710-RAZR_M-KITKAT recovery i also try mokee 4.4.3 but same stuck on bootloader.
ericerk said:
Are you Fastboot flashing?
Click to expand...
Click to collapse
I was, but in the end I followed @ATTACK 's advice and used the apps from the Play Store. My impatience and forgetfulness caused me to butt my head against a metaphorical brick wall a few times, but I managed.
Related
i updated it to modaco 6.2.2, don't know why but did a factory reset in the settings menu. it deleted everything. only left with twrp folder, still able to get into recovery. tried reflashing modaco zip, but says unable to open zip.
can i flash a stock rom?
Yes you should probably flash something. That's why you always make a backup
Sent from my Kindle Fire using xda premium
pete_kowalski83 said:
Yes you should probably flash something. That's why you always make a backup
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
made a backup and it erased that too. just tried cm7 with no success. will keep trying.
Ok, This happened to me on my DHD, Try to fastboot a recovery and flash it. Use the one doomlord made then Flash. BUT before you do that make sure to have the update on your sdcard.
every zip i tried says installed then when u reboot system it goes directly back twrp
nitty917 said:
every zip i tried says installed then when u reboot system it goes directly back twrp
Click to expand...
Click to collapse
I was in the same situation last month. The only solution for me was to flash the stock ROM and start over from scratch.
worldwidepmp said:
I was in the same situation last month. The only solution for me was to flash the stock ROM and start over from scratch.
Click to expand...
Click to collapse
where did you find the stock roms?
Im looking for a pre rooted one, the 6.2.2 link seems heavy traffic
nitty917 said:
where did you find the stock roms?
Im looking for a pre rooted one, the 6.2.2 link seems heavy traffic
Click to expand...
Click to collapse
I followed these instructions http://forum.xda-developers.com/showpost.php?p=20438599&postcount=1 I've never tried it with a pre-rooted ROM, so YMMV. Like I said I flashed this and started the root process over from scratch and this is what worked.
worldwidepmp said:
I followed these instructions http://forum.xda-developers.com/showpost.php?p=20438599&postcount=1 I've never tried it with a pre-rooted ROM, so YMMV. Like I said I flashed this and started the root process over from scratch and this is what worked.
Click to expand...
Click to collapse
thanks back to stock. will be more careful now.
worldwidepmp said:
I was in the same situation last month. The only solution for me was to flash the stock ROM and start over from scratch.
Click to expand...
Click to collapse
NOT TRUE. You are just stuck in recovery mode. View the thread for how to get out. I would post a link but I'm mobile..
Sent from my myTouch_4G_Slide using XDA App
jmcoffey said:
NOT TRUE. You are just stuck in recovery mode. View the thread for how to get out. I would post a link but I'm mobile..
Sent from my myTouch_4G_Slide using XDA App
Click to expand...
Click to collapse
??? You sure you're in the right thread?
too late anyways, I'm on 6.2.2 and having a hell of time to root with a mac.
worldwidepmp said:
??? You sure you're in the right thread?
Click to expand...
Click to collapse
absolutely right:
adb shell su -c "idme bootmode 4000"
adb reboot
done
hi guys.. i just flash clockworkmod on my galaxy w I8150 and now i want to remove it..
is anyone know how to remove it? thanks
See http://forum.xda-developers.com/showthread.php?t=1446593&page=6 here you will find the stock recovery file. You flash it the same way you flashed the custom recovery.
robin0800 said:
See http://forum.xda-developers.com/showthread.php?t=1446593&page=6 here you will find the stock recovery file. You flash it the same way you flashed the custom recovery.
Click to expand...
Click to collapse
If you need an instruction as well, use this link
http://forum.xda-developers.com/showthread.php?t=1467128
you will have to scroll down to Other.
greets
THE-E
robin0800 said:
See http://forum.xda-developers.com/showthread.php?t=1446593&page=6 here you will find the stock recovery file. You flash it the same way you flashed the custom recovery.
Click to expand...
Click to collapse
thanks... really help me..
Here is a n00b question !
Why flash Clockworkmod from links
here and not trough RomManager app from Market ?
Sent from my GT-I8150 using XDA App
polifemo said:
Here is a n00b question !
Why flash Clockworkmod from links
here and not trough RomManager app from Market ?
Sent from my GT-I8150 using XDA App
Click to expand...
Click to collapse
last time I checked Rom Manager did not support our phone!
Thanks robin0800
Sent from my GT-I8150 using XDA App
If i wanna flash the stock recovery, do i need to include the ancora.ops?
SyzwnFrzRdz said:
If i wanna flash the stock recovery, do i need to include the ancora.ops?
Click to expand...
Click to collapse
yes you do though feel free to drop the reboot time to 60 seconds for recovery and 120 seconds for a rom flash
SyzwnFrzRdz said:
If i wanna flash the stock recovery, do i need to include the ancora.ops?
Click to expand...
Click to collapse
Only if you flash with ODIN.....
If adb, using "dd" command, not necessary.
Sent from my GT-I8150 using Tapatalk
irishpancake said:
Only if you flash with ODIN.....
If adb, using "dd" command, not necessary.
Sent from my GT-I8150 using Tapatalk
Click to expand...
Click to collapse
True but I thought you did not like the "Data Destroying" command?
robin0800 said:
True but I thought you did not like the "Data Destroying" command?
Click to expand...
Click to collapse
Of course it can be used, but with care!!!
I agree....
there should always be a warning
http://en.wikipedia.org/wiki/Dd_(Unix)
It is jokingly said that dd stands for "disk destroyer", "data destroyer", "death and destruction", or "delete data", since when used for low-level operations on hard disks, a small mistake, such as reversing the if and of (input and output) parameters, could result in the loss of some or all data on a disk.
Click to expand...
Click to collapse
We already had one poor guy "brick" with "dd" misuse:
http://forum.xda-developers.com/showpost.php?p=22031410&postcount=1
I think he returned his phone under warranty, and hopes for the best.....
If you see this nemesis.sisemen.... I hope you got it sorted, man
thanks
This forum is great it helped me to learn so much about my phone
robin0800 said:
yes you do though feel free to drop the reboot time to 60 seconds for recovery and 120 seconds for a rom flash
Click to expand...
Click to collapse
Where do i edit the reboot time? And why is the time must be different dude?
irishpancake said:
Only if you flash with ODIN.....
If adb, using "dd" command, not necessary.
Sent from my GT-I8150 using Tapatalk
Click to expand...
Click to collapse
You mean in any version of Odin? Btw, is using adb method dangerous?
SyzwnFrzRdz said:
You mean in any version of Odin? Btw, is using adb method dangerous?
Click to expand...
Click to collapse
Man, you gotta do some reading......THE-E has a good guide to flashing with ODIN here
"dd" is only dangerous, like an auto-mobile, in the hands of those who cannot drive!!!
irishpancake said:
Man, you gotta do some reading......THE-E has a good guide to flashing with ODIN here
"dd" is only dangerous, like an auto-mobile, in the hands of those who cannot drive!!!
Click to expand...
Click to collapse
I read the forum before as i have made a bookmark of it in my browser. Actually, i'm confused because there's Odin Multi Downloader and the older one, right?
Sorry ,
but why would one want to remove
CWM ? Is there some issue with the software or is it a warrenty thing?
Apart from personal gusto, of course.
Sent from my GT-I8150 using XDA App
polifemo said:
but why would one want to remove
CWM ? Is there some issue with the software or is it a warrenty thing?
Click to expand...
Click to collapse
Because updating via OTA(OverTheAir) is (yet) only possible with the stock recovery.
greets
THE-E
sorry guys for this question, but the reason why i want to remove cwm because, if someday i had to sent my phone to the service center i must remove cwm, if they found out, maybe they will decline my phone..
Flash back stock FW...everything will be restored....
What's the point Binary count to show phone is rooted is there as I know Samsung don't bother if you have rooted in Malaysia.....
Sent from my GT-I8150 using xda premium
Hi guys, I am very new to this community and this is my first post. So this is what happened:
I had my One X for about 4 months now, and I was starting to want something new so I rooted it and unlocked the bootloader everything went just fine. So I realized root isn't the only big thing you can do to tweak your device so I wanted to flash a custom ROM. I wanted to customize it so I used this guide: http://forum.xda-developers.com/showthread.php?t=1611349 to customize CMOD 10 based on Jelly Bean and flash it to my device. So I finished my custom ROM and wanted to flash it to my device. So I used this guide: http://forum.xda-developers.com/showthread.php?t=2069904 (post 2 only (of course)).
At first when I tried to flash my custom ROM I didn't make any backup because I had Titanium backup and I thought that it does the same thing as recovery backup (now I know it doesn't) so I don't have the stock ROM on backup. I was disappointed that the device won't boot, it only shows the boot screen "HTC quietly brilliant". And then I saw boot.img I didn't knew what to do with it so I read about it and found out that I need to flash the boot.img before I flash the ROM. So I deleted everything again and done it all over again, but I flashed boot.img that came with the CM 10 first and then flashed the ROM itself. I've done everything correctly and my device still won't boot. It's over 20 minutes and still showing the "HTC quietly brilliant" like before the boot.img.
What should I do and very much thanks for the helpers I don't want to lose my device. :crying:
EDIT: I forgot to mention that this is my first android device.
Try - fastboot erase cache - while in fast boot
Sent from my HTC One X using xda premium
Clean install? Try to clear cache in recovery.
Boot to bootloader (voldown and power). On the top you should see hboot version. What is it?
Also, does fastboot say OKAY when boot.img is flashed?
Sent from my EndeavorU using xda app-developers app
cleancorekiller said:
Try - fastboot erase cache - while in fast boot
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Already tried it. And this is CM10 I downloaded it from their github can't be broken.
THX for the replay BTW.
revolve narytia
TToivanen said:
Clean install? Try to clear cache in recovery.
Boot to bootloader (voldown and power). On the top you should see hboot version. What is it?
Also, does fastboot say OKAY when boot.img is flashed?
Sent from my EndeavorU using xda app-developers app
Click to expand...
Click to collapse
Already tried to clear cache... A LOT.
HBOOT version is: 1.39.0000
And yes it does say OKAY when boot.img is flashed.
And I already tried clean install a lot.
Okay matey, here's your problem:
You need a special boot.img for your newer hboot version. Check post # 9308 in CM10 thread for link.
Unfortunately GPS doesn't work with this boot.img.
Edit: right post number
Sent from my EndeavorU using xda app-developers app
TToivanen said:
Okay matey, here's your problem:
You need a special boot.img for your newer hboot version. Check post # 1308 in CM10 thread for link.
Unfortunately GPS doesn't work with this boot.img.
Sent from my EndeavorU using xda app-developers app
Click to expand...
Click to collapse
You are my new god. I will pray for you everyday.
THANK YOU I will report if this will work. Do you know when or where will there be a one with working GPS?
Tomervutx said:
You are my new god. I will pray for you everyday.
THANK YOU I will report if this will work. Do you know when or where will there be a one with working GPS?
Click to expand...
Click to collapse
LOL, just click the thanks button.
Gps will be fixed when slow-ass HTC releases the JB kernel source code. Until then, you can use Trip's CM10 or IceColdJelly 4.2.1 for working GPS.
Sent from my EndeavorU using xda app-developers app
TToivanen said:
LOL, just click the thanks button.
Gps will be fixed when slow-ass HTC releases the JB kernel source code. Until then, you can use Trip's CM10 or IceColdJelly 4.2.1 for working GPS.
Sent from my EndeavorU using xda app-developers app
Click to expand...
Click to collapse
Mind sharing a link? will save me a lot of time.
link
TToivanen said:
link
Click to expand...
Click to collapse
You saved my life. Thank you again!
TToivanen said:
link
Click to expand...
Click to collapse
It's not working... I clean installed my customized CM10 ROM and then the boot.img you gave me. (I tried vice versa too). It's booting and then restarting to recovery mode.
Probably something went wrong when you customized it. What exactly did you do? Why not just download it as it is?
And when you talked about github.... you mean you built it from source?
TToivanen said:
Probably something went wrong when you customized it. What exactly did you do? Why not just download it as it is?
And when you talked about github.... you mean you built it from source?
Click to expand...
Click to collapse
I did built it form source. I got in a folder 3 files: 2 folders: system and META-INF 3rd file is boot.img.
I probably don't know what to put in update.zip (what folders) would you tell me?
I customized some colors, battery skin on the status bar and fonts. I also customized build.prop and added adrenaline script so I got another folder named "data".
could you tell me how to pack it all to update.zip? I guess my problem is that.
P.S. I also sign it after packing it to update.zip with auto-signer using java.
THX in advance!
Here's one idea: Download the pre built zip of the rom and use it as a template. Replace all the folders inside with your own, custom ones.
Sent from my EndeavorU using xda app-developers app
TToivanen said:
Here's one idea: Download the pre built zip of the rom and use it as a template. Replace all the folders inside with your own, custom ones.
Sent from my EndeavorU using xda app-developers app
Click to expand...
Click to collapse
I tried it this is the result... Don't you have an experience with ROM building?
Not sure if you understood correctly.
I meant you should dl the rom from get.cm and then replace the files with the ones you built and modified.
If this is exactly what you did, then I'm out of ideas.
I, in fact, haven't built a rom from source in my life.
Sent from my EndeavorU using xda app-developers app
TToivanen said:
Not sure if you understood correctly.
I meant you should dl the rom from get.cm and then replace the files with the ones you built and modified.
If this is exactly what you did, then I'm out of ideas.
I, in fact, haven't built a rom from source in my life.
Sent from my EndeavorU using xda app-developers app
Click to expand...
Click to collapse
I haven't built it from source. I downloaded the base CM10 mod and edited it's files and compressed and flashed to my device. But I am checking another option.
Why not flash the rom as it is and put your own stuff to system afterwards with adb or an file explorer ?
MeLViN-oNe said:
Why not flash the rom as it is and put your own stuff to system afterwards with adb or an file explorer ?
Click to expand...
Click to collapse
I am editing it with dsixda kitchen and I found out what was my problem... I added Adrenaline script and I need to add support to that through dsixda-android kitchen. Any idea how?
Will there eventually be an app for unlocking the bootloader on the 10.3 firmware? I don't have the factory cable and it sounds like a lot of people have bricked their device doing the downgrade to 10.2.
I hope so. I am not gonna even try it... Lol instead rooted it and used Kindlefree app to install Nova and used titanium backup. So it's "like" Android but not quite lol....
Sent from my Nexus 4 using xda app-developers app
It worked for me even with the 10.3.1 bootloader. It seems that the exploit is not closed yet.
Sent from my A2109A using Tapatalk HD
I can confirm that the utilities still work fine with the latest version of the kindle software, so you shouldn't even need to downgrade.
flopower1996 said:
It worked for me even with the 10.3.1 bootloader. It seems that the exploit is not closed yet.
Sent from my A2109A using Tapatalk HD
Click to expand...
Click to collapse
But if I downgrade my bootloader I won't have to use the whole 2nd bootloader method and all that right? Won't I then just be able to use some utility to flash TWRP and then flash a ROM? This Kindle thing is probably a little more intimidating than anything else I've messed with. I have mine rooted and a bunch of other hacks but I want pure Android on. I don't want a brick though..
Sent from my Nexus 4 using xda app-developers app
---------- Post added at 01:58 PM ---------- Previous post was at 01:58 PM ----------
jwort93 said:
I can confirm that the utilities still work fine with the latest version of the kindle software, so you shouldn't even need to downgrade.
Click to expand...
Click to collapse
Which utility did you use and did you need a fastboot cable?
Sent from my Nexus 4 using xda app-developers app
You're going to need the second boot loader no matter what
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mindmajick said:
You're going to need the second boot loader no matter what
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Ok so if I use this http://forum.xda-developers.com/showthread.php?t=2216285 to downgrade my current bootloader then use this http://forum.xda-developers.com/showthread.php?t=2106463 to flash the freedom boot img and TWRP then I can just flash a ROM like normal through TWRP. Right?
Sent from my Nexus 4 using xda app-developers app
jcnbama said:
Ok so if I use this http://forum.xda-developers.com/showthread.php?t=2216285 to downgrade my current bootloader then use this http://forum.xda-developers.com/showthread.php?t=2106463 to flash the freedom boot img and TWRP then I can just flash a ROM like normal through TWRP. Right?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
No need to downgrade the bootloader. Install the apk from the dev. Thread and click install. Nothing else.
Sent from my A2109A using Tapatalk HD
flopower1996 said:
No need to downgrade the bootloader. Install the apk from the dev. Thread and click install. Nothing else.
Sent from my A2109A using Tapatalk HD
Click to expand...
Click to collapse
What about all that craziness I have been reading about locking up the bootloader due to the 10.3.1 bootloader? I can just forget about that and install that apk file and THEN I would be able to flash a ROM via TWRP? I thought that the thread said that this tool said it was for the old bootloader. This is great news! Can you confirm this? Are we on the same page?
Sent from my KFOT using xda app-developers app
jcnbama said:
What about all that craziness I have been reading about locking up the bootloader due to the 10.3.1 bootloader? I can just forget about that and install that apk file and THEN I would be able to flash a ROM via TWRP? I thought that the thread said that this tool said it was for the old bootloader. This is great news! Can you confirm this? Are we on the same page?
Sent from my KFOT using xda app-developers app
Click to expand...
Click to collapse
Yes the exploit stil exists. Tested by myself withe the 10.3.1 bootloader and confirmed by other people. Enjoy the freedom of flashing!
Sent from my A2109A using Tapatalk HD
flopower1996 said:
Yes the exploit stil exists. Tested by myself withe the 10.3.1 bootloader and confirmed by other people. Enjoy the freedom of flashing!
Sent from my A2109A using Tapatalk HD
Click to expand...
Click to collapse
Oh my goodness. This absolutely worked. WHY didn't I meet you like 3 days ago? LOL Any noob to Kindle should know about this. Root + Run a simple .apk WOW. Any thoughts on the best Rom going right now for KF2? Kernel?
jcnbama said:
Oh my goodness. This absolutely worked. WHY didn't I meet you like 3 days ago? LOL Any noob to Kindle should know about this. Root + Run a simple .apk WOW. Any thoughts on the best Rom going right now for KF2? Kernel?
Click to expand...
Click to collapse
Well, i personally use the aosp Rom by hashcode. It`s simple, nice and clean. But what you are using is your own choice. Flash different Roms and make your own mind.
Sent from my A2109A using Tapatalk HD
flopower1996 said:
Well, i personally use the aosp Rom by hashcode. It`s simple, nice and clean. But what you are using is your own choice. Flash different Roms and make your own mind.
Sent from my A2109A using Tapatalk HD
Click to expand...
Click to collapse
So, it looks like I have screwed something up. This figures as my luck is terrible with this freegin Kindle. So I got TWRP recovery working fine. I DL Cyanogenmod 10.1 and Gapps accordingly. Went into TWRP of course made a backup, then went to flash. I wiped EVERYTHING and went to flash the ROM. I received the error <Could Not Open .zip> So now I have nothing on file except a bad .zip. I did re-download the ROM assuming it was bad and restored my TWRP backup. Now I am stuck in what appears to be a Kindle Bootloop. The Kindle Fire (Orange) logo comes up, a few seconds later it blinks back off again and recycles. Now what? I can't get the Kindle to boot so I can put the .zip back on the machine. I am STUCK. This sucks... :crying:
jcnbama said:
So, it looks like I have screwed something up. This figures as my luck is terrible with this freegin Kindle. So I got TWRP recovery working fine. I DL Cyanogenmod 10.1 and Gapps accordingly. Went into TWRP of course made a backup, then went to flash. I wiped EVERYTHING and went to flash the ROM. I received the error <Could Not Open .zip> So now I have nothing on file except a bad .zip. I did re-download the ROM assuming it was bad and restored my TWRP backup. Now I am stuck in what appears to be a Kindle Bootloop. The Kindle Fire (Orange) logo comes up, a few seconds later it blinks back off again and recycles. Now what? I can't get the Kindle to boot so I can put the .zip back on the machine. I am STUCK. This sucks... :crying:
Click to expand...
Click to collapse
You have fastboot cable?
--
Sent from my mind to your screen.
mindmajick said:
You have fastboot cable?
--
Sent from my mind to your screen.
Click to expand...
Click to collapse
It's on the way lol. Ordered it today. What is terrible is I thought I was doing the right thing by doing a backup up TWRP. Just in case ya know? It *usually* works. Now I just need to know the next steps so I can get back where I need to be. Thought I was home free with TWRP.
Sent from my Nexus 4 using xda app-developers app
jcnbama said:
It's on the way lol. Ordered it today. What is terrible is I thought I was doing the right thing by doing a backup up TWRP. Just in case ya know? It *usually* works. Now I just need to know the next steps so I can get back where I need to be. Thought I was home free with TWRP.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I did the exact same thing when i got my kindle back in January. (Yeah, i had to order my cable right after that )
For some reason I've never been able to restore a stock TWRP backup on the kf2. It always borks the bootloader.
I know there is a special requirement that our bootloader uses a file called stack on the system partition- that's why you can't get into recovery now (when you wiped the system it wiped the stack file which let's us run the second bootloader.)
Anyway, Once you have the fastboot cable its really easy to get things going again. Pm me if you need a hand.. I've been through this myself a few times lol.
If you ever end up in the same situation again where you wiped the system and the zip is bad... Stay in twrp and use "adb sideload" to push a good zip from pc.
--
Sent from my mind to your screen.
mindmajick said:
I did the exact same thing when i got my kindle back in January. (Yeah, i had to order my cable right after that )
For some reason I've never been able to restore a stock TWRP backup on the kf2. It always borks the bootloader.
I know there is a special requirement that our bootloader uses a file called stack on the system partition- that's why you can't get into recovery now (when you wiped the system it wiped the stack file which let's us run the second bootloader.)
Anyway, Once you have the fastboot cable its really easy to get things going again. Pm me if you need a hand.. I've been through this myself a few times lol.
If you ever end up in the same situation again where you wiped the system and the zip is bad... Stay in twrp and use "adb sideload" to push a good zip from pc.
--
Sent from my mind to your screen.
Click to expand...
Click to collapse
I actually tried the side load through TWRP. When I typed "adb devices" it showed my device in host mode and the file wouldn't transfer although TWRP was in adb sideload mode. But then I just thought "oh well guess I'll restore my backup" lol. Yeah that didn't work out..
Sent you a P. M. BTW. thanks again!
Sent from my Nexus 4 using xda app-developers app
Thanks for the info guys. I'm glad I didn't have to change the firmware. The whole process was super easy and now I'm running jb 4.2. For those reading, just root->install one touch apk->make backup in twrp->factory reset->flash rom and gapps->success!
punkcitykid said:
Thanks for the info guys. I'm glad I didn't have to change the firmware. The whole process was super easy and now I'm running jb 4.2. For those reading, just root->install one touch apk->make backup in twrp->factory reset->flash rom and gapps->success!
Click to expand...
Click to collapse
**As a special note however DO NOT restore your factory backup if you have trouble. You will end up like me. Bootlooping with a fast boot cable in the mail.** if I could go back in time I would've downloaded the files via a hard line rather than slow wifi and maybe even double downloaded.. Oh well. This is a learning opportunity.
Sent from my Nexus 4 using xda app-developers app
i flashed the rocovery through odin so i can root. can i flash the official CWM recovery over this? would like to stay updated through rom manager if possible. thanks for any help
mike216 said:
i flashed the rocovery through odin so i can root. can i flash the official CWM recovery over this? would like to stay updated through rom manager if possible. thanks for any help
Click to expand...
Click to collapse
If you're rooted you should be able to install rom manager, and then install CWM from there.
Toleraen said:
If you're rooted you should be able to install rom manager, and then install CWM from there.
Click to expand...
Click to collapse
im already on CWM but i want the official through rom manager. i flashed a recoveryimg. from the odin flashable thread
If you install Rom Manager while rooted, go into the app, it should install the official CWM over your current install.
Sent from my SGH-M919 using xda premium
Toleraen said:
If you install Rom Manager while rooted, go into the app, it should install the official CWM over your current install.
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
thanks thats what i was waiting to hear
U should press the thanks button, just sayin.
Sent from my SGH-M919 using xda app-developers app
I still don't see why anyone would rather have CWM over TWRP.... just sayin'
TeknoGodz said:
I still don't see why anyone would rather have CWM over TWRP.... just sayin'
Click to expand...
Click to collapse
I've never used it. What's the advantage of TWRP over CWM?
Sent from my SGH-M919 using xda premium
TeknoGodz said:
I still don't see why anyone would rather have CWM over TWRP.... just sayin'
Click to expand...
Click to collapse
I loved TWRP when I was on the S3, but on the S4 it appears to be too sensitive. When I try to install a zip file and scroll down the list of folder using my finger it will enter that folder i did not pick.
dhonzik said:
I loved TWRP when I was on the S3, but on the S4 it appears to be too sensitive. When I try to install a zip file and scroll down the list of folder using my finger it will enter that folder i did not pick.
Click to expand...
Click to collapse
It will be fixed
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I have many app ideas, but don't have the skill or the time to learn how to make an app. if you would like to know an idea and attempt to make one, just message me.
ArianaGrande said:
It will be fixed
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I have many app ideas, but don't have the skill or the time to learn how to make an app. if you would like to know an idea and attempt to make one, just message me.
Click to expand...
Click to collapse
Great, I'll switch back when that is fixed. Right now I am using the OUDHS CWM based Recovery cause the text is readable. The text in the regular CWM is too tiny to read, I have to use a magnifying glass to read the options
Toleraen said:
I've never used it. What's the advantage of TWRP over CWM?
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
Honestly, just about everything. Just look at pictures of it and you'll see.
dhonzik said:
I loved TWRP when I was on the S3, but on the S4 it appears to be too sensitive. When I try to install a zip file and scroll down the list of folder using my finger it will enter that folder i did not pick.
Click to expand...
Click to collapse
Yes, there is an issue with that since the touch screen is so much more sensitive on the S4, but it will be fixed soon. Team Win is working on it.