Related
Hello,
Right now I have the stock FRF85B build on my nexus one. I want su and superuser, nothing else. I have already unlocked the bootloader. What do I do from here.?I do not want to install custom ROMs at this point.
Go to erasethis.net/wordpress I wrote an entry today similar to what you want includes links
disgustip8ted said:
Go to erasethis.net/wordpress I wrote an entry today similar to what you want includes links
Click to expand...
Click to collapse
That's great - but didn't you start with a custom recovery?
Can you drop a custom recovery on a stock recovery for FRF85B without the right Superboot?
I ask, because I am also stuck with this stock build and recovery. And when I read the instructions for installing Amon_RA, one of the prerequisites is Superboot. The problem is that there is no Superboot for this build yet.
HALP! I feel like I'm stuck in a chicken-and-egg scenario.
Ah I forgot that part. Wrote that up while at work. Inthe last section there is a link to the page where lox posts an update.zip for root access. I opened the zip and extracted the boot.img and flashed that I think,then I flashed the recovery for amon-ra.
After that is when I put the update.zip from lox on and flashed his update.zip for root access with the such utility.
The method posted in the dev section works perfectly. Root without unlocking. Then you can install a custom recovery/rom if you want.
__________________________________
N1 w/ XDA App
I second this post. I am in the EXACT same situation as the original poster and I'm frankly embarrassed that I can't figure out what to do next.
If we're making huge requests, can you write it up for mac users? There is a surprising lack of documentation for us. I hope this doesn't open me up to a flamewar - if it counts for anything I've been lustily eying windows 7..
edit: I'm an idiot and had not googled the right question. If you run a mac, and have the bootloader unlocked already please see this link:
http://theonda.org/articles/2010/03...-performance-boost-and-some-serious-geek-cred
use your brains to suss out the relevant directions, make sure you have a more updated version of ROM Manager or RA or whatever custom recovery you want and basically just ignore the stuff about custom radios etc. You're basically just using the terminal (or whatever windows / linux does) to flash the custom firmware back on.
Again if you have the bootloader already unlocked (icon appears on startup), just find generic directions for your OS on how to install custom recovery. On the mac, it's simply few terminal commands using the fastboot program linked off the page linked above.
Sorry I can't be of more help - i have to be up early and it's pushing midnight.
Pretty much a redundant thread, seeing as everyone is doing it now. (But not before I ported the method from SGS II by Phil 3759 http://forum.xda-developers.com/member.php?u=4666971 )
Still makes interesting reading though.....
Thank you for your feedback and link here
But your post links are broken as you copy pasted and forum shortcuts them
So, original thread here:
http://forum.xda-developers.com/showthread.php?t=1746794
Also linked in my signature
Please, ask questions there, I will not monitor this thread for support, so cannot answer questions
Phil3759 said:
Thank you for your feedback and link here
But your post links are broken as you copy pasted and forum shortcuts them
So, original thread here:
http://forum.xda-developers.com/showthread.php?t=1746794
Also linked in my signature
Please, ask questions there, I will not monitor this thread for support, so cannot answer questions
Click to expand...
Click to collapse
Thank you - (fixed it)
shoey63 said:
Possibly the easiest method yet! (Unless you want to PC Odin custom kernel and use potentially dangerous Triangle away to reset counter and get rid of yellow triangle)
1) Download this file:- http://forum.xda-developers.com/attachment.php?attachmentid=1256643&d=1344771266 (comes from this thread - http://forum.xda-developers.com/showthread.php?t=1746794 Kudos to Phil 3759)
2) Copy to external SD card
3) Reboot into stock recovery and select "apply update from external storage"
4) Select "CWM_Root_SuperSU.0.94-Busybox.1.20.2-S2-signed.zip" and wait for Superuser and Busybox to install
5) Go back and reboot system.
Done! You now have fully rooted stock ICS (works on 4.04). Don't forget you are also on stock kernel so NO WIPING!!!
If u want custom kernel, use mobile Odin afterwards.
(BTW dont forget to open superSU after reboot to update binary)
Click to expand...
Click to collapse
That's not rooting - that's rooting AND installing busybox. Sometimes installing busybox can cause problems on a device.
To root, it's simple:
Go to Chainfire's SuperSU thread
Download the latest "CWM-flashable" version
Put on external SD
Flash from recovery
This WON'T also add busybox which can sometimes cause problems.
The reason this works: With ICS updates for I9100/N7000/I777/probably others, Samsung started permitting ZIPs signed with testkeys to be flashed from recovery.
This does not appear to work on newer devices - fails on N8000/N8013 for example.
Hello,
Does this mean if I do this to my note running N7000DDLR6 (don't if its required to mention this), I'll be able to under-clock it and remove system apps without anything more? and that It will be totally safe?
what precautions need to be taken while doing this and after that?
Regards
Sujai
sujaishukla said:
Hello,
Does this mean if I do this to my note running N7000DDLR6 (don't if its required to mention this), I'll be able to under-clock it and remove system apps without anything more? and that It will be totally safe?
what precautions need to be taken while doing this and after that?
Regards
Sujai
Click to expand...
Click to collapse
Ofcourse not, after rooting you are not safe anymore.
If you delete something vital your phone won't boot anymore.
So only root after reading and understanding what you are doing or intent to do...
Entropy512 said:
That's not rooting - that's rooting AND installing busybox. Sometimes installing busybox can cause problems on a device.
...
This WON'T also add busybox which can sometimes cause problems.
Click to expand...
Click to collapse
It can be true under some circumstances, but:
- Many good applications will not run without busybox installed in /system/xbin. Some can chose to go without them, others no. Until developers start including their busybox under their app folder (like Titanium Backup), there will be no other choice if you do need those applications
- Without busybox, you loose a lot of commands under the terminal console. End users do not care, until they need debugging...
- CWM recovery installs busybox in /sbin, it is even completely built into his recovery. So, every time you have cwm installed, you end up with busybox (Most if not all custom kernels/ROMs are concerned that way, include CF-Root kernels...)
- Installing busybox from a market installer is a real mess while installing it through a recovery script can be fully undone
Entropy512 said:
...
Click to expand...
Click to collapse
I'm sorry, but wasn't the CWM.zip the problem for fast few weeks? How come out of nowhere it's "OK" to install the flashable/temporary CMW and it is the Busybox causing the problem?
Please make it clear - is it the CMW.zip counting as "Unsafe" or it is something else?
Spo0f said:
I'm sorry, but wasn't the CWM.zip the problem for fast few weeks? How come out of nowhere it's "OK" to install the flashable/temporary CMW and it is the Busybox causing the problem?
Please make it clear - is it the CMW.zip counting as "Unsafe" or it is something else?
Click to expand...
Click to collapse
The root methods mentioned above can be done from stock recovery skipping the cwm temporary step
Busybox can cause issues with some applications that rely on a generic busybox copy under /system/xbin
This is caused by the fact that each busybox build can have different valid commands. The application cannot know if the commands it needs are supported unless it is bundled with its own busybox copy. It will rely on the compiler of busybox to implement the commands.
Until now, I never encountered such problems with last busybox, but, it doesn't mean one of your apps will never behave strangely...
This is a problem related to the application its self, not busybox specifically
So to summarize this in clear words for note users it should be:
-Note users can easily get root only by flashing supersu or superuser (CWM flashable zips) through stock rom recovery directly,no need for CWM.ZIP at all.
-Note users can also get root + busybox by flashing CWM.ZIP old safe non touch v 4.x through stock recovery first,then to flash supersu/superuser+busybox zip through the temp CWM 4.
Am i right guys? plz do confirm...
Also what about wiping now through temp CWM4 with ICS rooted stock kernel? is it safe now??
↖(^▽^)↗ Sent from Rego Galaxy Note ↖(^▽^)↗
Entropy512 said:
That's not rooting - that's rooting AND installing busybox....
Click to expand...
Click to collapse
OK thanks, forgot to mention that, I'll amend OP
Already answered
eng.rego said:
So to summarize this in clear words for note users it should be:
-Note users can easily get root only by flashing supersu or superuser (CWM flashable zips) through stock rom recovery directly,no need for CWM.ZIP at all.
-Note users can also get root + busybox by flashing CWM.ZIP old safe non touch v 4.x through stock recovery first,then to flash supersu/superuser+busybox zip through the temp CWM 4.
Am i right guys? plz do confirm...
Also what about wiping now through temp CWM4 with ICS rooted stock kernel? is it safe now??
↖(^▽^)↗ Sent from Rego Galaxy Note ↖(^▽^)↗
Click to expand...
Click to collapse
All is ok, except wipe
I cannot certify it is safe. Entropy512 which is involved in CM dev said it is safe for CWM4. I never tested, cannot confirm
Also, CWM6 is still unknown state on stock kernel, until some dev can confirm it
eng.rego said:
So to summarize this in clear words for note users it should be:
-Note users can easily get root only by flashing supersu or superuser (CWM flashable zips) through stock rom recovery directly,no need for CWM.ZIP at all.
Click to expand...
Click to collapse
Correct.
eng.rego said:
-Note users can also get root + busybox by flashing CWM.ZIP old safe non touch v 4.x through stock recovery first,then to flash supersu/superuser+busybox zip through the temp CWM 4.
Click to expand...
Click to collapse
Haven't tried it that way because it involves an extra unnecessary flash. Anyway best to steer clear of any CWM.zip. I bricked my note wiping on touch version. Why use it if u don't have too?
but ultimately we have to used odin to flash a safe kernel after this proceedure.
can we use this to 'cure' the 'partial root' phenomenon many face after flashing even recent ics custom roms ?
i admit installing busybox from market successfully can be a real pain .....
we need busybox for many things like supercharger script etc etc
some apps wont work if you dont have the upgraded version of bb
Some like to stay on stock Ics kernel because of stability. (only unsafe if wipes are performed on them) If u want custom kernel then obviously mobile odin pro/lite is the way to go. At least this way u dont raise flash counter and then have to use potentially dangerous triangle away app. As far as "partial root" goes - not sure. It will install SuperSU. Just open it to update binary and uninstall any other superuser apps that are already on phone
Sent from my GT-N7000 using xda app-developers app
Let me get this straight:
The "official" root thread for Note [02Feb12]How to Root/Unroot Samsung Galaxy Note + CWM says this:
Using CWM.zip (temporary/Touch recovery)method to root is said to be unsafe by entropy, and till safe release don't use it
Read This http://forum.xda-developers.com/show....php?t=1810954
Click to expand...
Click to collapse
Now there is new release which is CWM 6.
Is the old method safe with the new release?
No need for ANY CWM.zip (safe or not). Just flash file in OP on stock kernel recovery from external sd card. Job done .
Sent from my GT-N7000 using xda app-developers app
Yes... Can confirm this has worked for me... Followed instructions in OP, and copied the Uninstaller to my SD Card in the even that I need to return the phone... Flashed in Stock Recovery, rooted and done..
Thanks a million for this...:good:
New Procedure updating to My this thread in 1 hr ( I am working on it)
http://forum.xda-developers.com/showthread.php?t=1329360
new method based on What Entropy have guided us few post back
No need to use CWM at all
No need to flash SUperSU busybox installer (as Entropy said this can cause problem)
Disclaimer
I am not responsible to what damage happens to your phone while following this tutorial.
You are free to follow this or not follow this tutorial.I do not force anyone to try this.You are trying this on your own risk
Click to expand...
Click to collapse
As per the files given by @ron580 here I have compiled a CWM recovery for your BLU VIVO AIR
Instructions ==>
1-)Download the Mobileuncletools from google play.
2-)Download the recovery image from below.
3-)Place it in root of sdcard
4-)Open MOBILEUNCLE TOOLS and choose recoveru update option
5-)Then chose the recovery file and reboot to recovery.
I strongly recommend to not try this unless you know how to repair your phone in worst cases
abhishekr700 said:
As per the files given by @ron580 here I have compiled a CWM recovery for your BLU VIVO AIR
Instructions ==>
1-)Download the Mobileuncletools from google play.
2-)Download the recovery image from below.
3-)Place it in root of sdcard
4-)Open MOBILEUNCLE TOOLS and choose recoveru update option
5-)Then chose the recovery file and reboot to recovery.
I strongly recommend to not try this unless you know how to repair your phone in worst cases
Click to expand...
Click to collapse
Nice ^.^ ... i will get your CWM and compare with Chinese CWM to be sure about don't get any error... if you can compare to get sure about compatibility to don't brick the phone :highfive:
... you can have sure about checking the TWRP from Kazam Tornado 348 too ;D
DvDwx. said:
Nice ^.^ ... i will get your CWM and compare with Chinese CWM to be sure about don't get any error... if you can compare to get sure about compatibility to don't brick the phone :highfive:
... you can have sure about checking the TWRP from Kazam Tornado 348 too ;D
Click to expand...
Click to collapse
It would be a great help if u could do it
Because im a little more busy with my studies
Sent from my C2305 using Tapatalk
abhishekr700 said:
It would be a great help if u could do it
Because im a little more busy with my studies
Sent from my C2305 using Tapatalk
Click to expand...
Click to collapse
when i get time i can check that ;D... i'm busy too =#
we can use another recovery's too... because we just stay looking what already have developed on XDA... BUT we have Developers on other forums... like 4PDA(RUSSIA), Gionee Forum, BBS(Chinese) and a lot of others... we need can try make a Index Inside XDA to push Other Development projects from other forums to be more easy to get a better community to can have more projects running... for example: CWM already have been developed on Chinese and Russian Forums and TWRP already have been developed to Kazam Tornado 348.. and that is to SAME PHONE... Just using another name/Brand =#
we need push XDA ADM/GM's to make a generic page to our phone... because he have too much Brand/Names but is exactly same phone and hardware =#
...
but anyway is awesome get someone already developing any project on xda.. don't give up this phone, he is powerful and we maybe can get CUSTOM KERNEL from Spanish TeamForce Developer team.. we just need flood them to demonstrate interest about that phone.. :highfive:
Noone dared.to try it
?????
Sent from my C2305 using Tapatalk
abhishekr700 said:
Noone dared.to try it
?????
Sent from my C2305 using Tapatalk
Click to expand...
Click to collapse
I'm not in the position to test at the moment, sorry.
I will try but dont want to brick my device
Ilxaot said:
I'm not in the position to test at the moment, sorry.
Click to expand...
Click to collapse
PowSniffer0110 said:
I will try but dont want to brick my device
Click to expand...
Click to collapse
Hmm well guyz you gotta try it once but after you get a tutorial for flashing the stock rom on your device.
Deleted. My mistake of not knowing
DUHAsianSKILLZ said:
... guess no on wants a recovery. I dont own the device but, it should only break recovery if it fails. You can simply backup your stock recovery in flashify, and also, with a few commands typed in terminal.. You can create an image dump so you can flash incase you get into bootloops(unsure if it works). I have flashed many broken recoveries before and never had an hardbrick. Im not sure if BLU has download mode on their device but, as long you can reboot into that, you should be fine. Im unsure if there are any stock roms out right now.
Click to expand...
Click to collapse
Not a fair statement from someone that doesn't own the device It is very difficult to get adb running for this phone consistently. Additionally, backing up stock recovery fails using flashify. Lastly, I did attempt to flash this this morning with the recommended app from the OP and flashify and this is the recovery it booted to afterwards, which looks like the stock recovery (correct me if I am wrong).
Milly7 said:
Not a fair statement from someone that doesn't own the device It is very difficult to get adb running for this phone consistently. Additionally, backing up stock recovery fails using flashify. Lastly, I did attempt to flash this this morning with the recommended app from the OP and flashify and this is the recovery it booted to afterwards, which looks like the stock recovery (correct me if I am wrong).
Click to expand...
Click to collapse
that is the stock recovery... you can try use the KAZAM Tornado 348 TWRP, because they are the same phone and Share the same SDK to build Kernel and Another Boot images, if that don't work just flash your backup over it using ADB/fastboot
:highfive:
From 4dpa they have CWM and Carliv CWM working... but the best recovery to them is the official TWRP from Kazam Tornado 348
DvDwx. said:
that is the stock recovery... you can try use the KAZAM Tornado 348 TWRP, because they are the same phone and Share the same SDK to build Kernel and Another Boot images, if that don't work just flash your backup over it using ADB/fastboot
:highfive:
From 4dpa they have CWM and Carliv CWM working... but the best recovery to them is the official TWRP from Kazam Tornado 348
Click to expand...
Click to collapse
The point I am making is it appears that theses apps are not writing to our recovery partition. I will try to grab a log later if I can get adb running with this phone. I flashed the recovery in the OP several times and trying several apps.
Can you link to the recovery you are speaking of? I tried this because I was willing to chance it for the community.
Milly7 said:
The point I am making is it appears that theses apps are not writing to our recovery partition. I will try to grab a log later if I can get adb running with this phone. I flashed the recovery in the OP several times and trying several apps.
Can you link to the recovery you are speaking of? I tried this because I was willing to chance it for the community.
Click to expand...
Click to collapse
this "apps" work to our recovery partition because they are the SAME PHONE... Same SoC... Same Manufacture project(From Gionee) I'm Running TWRP from KAZAM here... you can give a try without problems :highfive:
if your phone don't stay be recognized on computer try follow the steps on my Root Topic to get ADB driver Working Correctly... but if after install the ADB driver it don't get work you need reset the ADB.exe cache on computer...
just open CMD and run this code: taskkill /F /T /IM adb.exe
then try run the code: "ADB Devices" inside the folder where stay installed the ADB (if you follow my steps on C:\adb\ you will get it)
and Turn OFF the 3rd Firewall security Programs on windows to get fully access to ADB Daemon Service :highfive:
DvDwx. said:
this "apps" work to our recovery partition because they are the SAME PHONE... Same SoC... Same Manufacture project(From Gionee) I'm Running TWRP from KAZAM here... you can give a try without problems :highfive:
if your phone don't stay be recognized on computer try follow the steps on my Root Topic to get ADB driver Working Correctly... but if after install the ADB driver it don't get work you need reset the ADB.exe cache on computer...
just open CMD and run this code: taskkill /F /T /IM adb.exe
then try run the code: "ADB Devices" inside the folder where stay installed the ADB (if you follow my steps on C:\adb\ you will get it)
and Turn OFF the 3rd Firewall security Programs on windows to get fully access to ADB Daemon Service :highfive:
Click to expand...
Click to collapse
I just saw your tutorial. I should be good still on one of my computers so that's a minor issue. I want you to link me to the Kazam recovery that may be compatible with our ViVo air so that I can test it. Thanks.
Milly7 said:
I just saw your tutorial. I should be good still on one of my computers so that's a minor issue. I want you to link me to the Kazam recovery that may be compatible with our ViVo air so that I can test it. Thanks.
Click to expand...
Click to collapse
---
I Suggest to you only give a try on TWRP because this project is OFFICIAL Supported by their team partners ;D
---
Alright ;D i will pass to you the links to get it
KAZAM Tornado 348 General Topic on XDA: LINK
OFFICIAL TWRP to KAZAM Tornado 348: LINK
OFFICIAL TWRP PAGE FROM THIS PHONE: LINK
GET boot.IMG to flash from HERE (Official repositories)
How to Install ... i get it from 4PDA RUSSIAN forum... just use google translator or Yandex.Translate to get it from russian to English ;D LINK
if you want try CWM from they -> LINK
or if you want try CARLIV CWM From they -> LINK
(* On top of their topics they have a Replay fixed with INDEX about already they discuss... there have everything linked to developments projects already shared ;D)
:highfive:
DvDwx. said:
---
I Suggest to you only give a try on TWRP because this project is OFFICIAL Supported by their team partners ;D
---
Alright ;D i will pass to you the links to get it
KAZAM Tornado 348 General Topic on XDA: LINK
OFFICIAL TWRP to KAZAM Tornado 348: LINK
OFFICIAL TWRP PAGE FROM THIS PHONE: LINK
GET boot.IMG to flash from HERE (Official repositories)
How to Install ... i get it from 4PDA RUSSIAN forum... just use google translator or Yandex.Translate to get it from russian to English ;D LINK
if you want try CWM from they -> LINK
or if you want try CARLIV CWM From they -> LINK
(* On top of their topics they have a Replay fixed with INDEX about already they discuss... there have everything linked to developments projects already shared ;D)
:highfive:
Click to expand...
Click to collapse
I hope the OP doesn't mind our chatter. I was able to flash the Twrp but it isn't without its issues. It is giving problems mounting cache and data when trying to wipe. I made a couple of backups and flashed a version of MIUI that I found in the Blu google + community. I was going to restore to stock but couldn't get Twrp to completely power off the device. Eventually data wiped and MIUI booted. Will check to see if I can restore a backup tomorrow.
Milly7 said:
I hope the OP doesn't mind our chatter. I was able to flash the Twrp but it isn't without its issues. It is giving problems mounting cache and data when trying to wipe. I made a couple of backups and flashed a version of MIUI that I found in the Blu google + community. I was going to restore to stock but couldn't get Twrp to completely power off the device. Eventually data wiped and MIUI booted. Will check to see if I can restore a backup tomorrow.
Click to expand...
Click to collapse
on 4PDA they have the BLU Firmware to install via CWM... if you want try it using TWRP... Here the LINK ... they say to Wipe everything to flash it...
(You don't format Cache and Data to F2FS... because the KitKat don't Support it to Run)
--
To me the 2.8.5.0 TWRP from KAZAM stay Working Correctly, i already format SDcard, Cache and Dalvik cache.. and make it don't bring problems to me... on 4PDA they talk about NVRAM problem... i don't know how to solve it but is easy to talk to they using translators ... there they have the Updated MiUi too... but if you have Backup your phone.. Use that ;D
DvDwx. said:
on 4PDA they have the BLU Firmware to install via CWM... if you want try it using TWRP... Here the LINK ... they say to Wipe everything to flash it...
(You don't format Cache and Data to F2FS... because the KitKat don't Support it to Run)
--
To me the 2.8.5.0 TWRP from KAZAM stay Working Correctly, i already format SDcard, Cache and Dalvik cache.. and make it don't bring problems to me... on 4PDA they talk about NVRAM problem... i don't know how to solve it but is easy to talk to they using translators ... there they have the Updated MiUi too... but if you have Backup your phone.. Use that ;D
Click to expand...
Click to collapse
Maybe that's the problem. I flashed 2.8.6.0. I am going to switch now.
Milly7 said:
Maybe that's the problem. I flashed 2.8.6.0. I am going to switch now.
Click to expand...
Click to collapse
... i don't give i try yet on 2.8.6.0 ... #sorry
maybe that is the problem...
---
i'm testing right now my alpha test pack with sony apps to get our phone more Classy ;D
DvDwx. said:
... i don't give i try yet on 2.8.6.0 ... #sorry
maybe that is the problem...
---
i'm testing right now my alpha test pack with sony apps to get our phone more Classy ;D
Click to expand...
Click to collapse
Awesome. And stay away from 2.8.6.0 for now. 2.8.5.0 worked much better.
Greetings-
I am able to root, and install twrp on my phone just fine. But I am not having much luck with Clockwordmod. I found this link which is a very organized, and comprehensive list of software including CWM. It points to this one, which points to this. My question is I don't know which file to pick. And for some reason Odin does not recognize the one I downloaded. I tried to flash the file with flashify, but I get into a boot loop. Can anyone point me to procedures and files which worked for this platform? I am running N900PVPUCNC5_N900PSPTCNC5_SPR. The main CWM site only seems to have the latest version, which is not odin compatible, and I am not sure if it works with my phone's software. I think it is meant for lollipop?
sansari123 said:
Greetings-
I am able to root, and install twrp on my phone just fine...
Click to expand...
Click to collapse
If you have TWRP why do you want CWM? They do the same function.
Journyman16 said:
If you have TWRP why do you want CWM? They do the same function.
Click to expand...
Click to collapse
Thanks. My understanding is I can not flash a zImage with twrp, but I can do it with CWM. Is that not correct? The reason I just want to flash the zImage is I want to eliminate some of the steps, and see why my image does not work.
sansari123 said:
Thanks. My understanding is I can not flash a zImage with twrp, but I can do it with CWM. Is that not correct? The reason I just want to flash the zImage is I want to eliminate some of the steps, and see why my image does not work.
Click to expand...
Click to collapse
I'm not sure what a zimage is - but normal image (img) files can be flashed in TWRP.
zimage is the kernel .
I am afraid this does not help me. Don't mean to be unappreciative. I have done some research, and saw somewhere CWM can flash zImage. I have not seen the same comment about TWRP; I tried it regardless. TWRP does not recognize zImage format. I have looked into reformating the file, but I have to rely on scripts, and I am not sure if the issue with my image is in the packing stage or something else. I want to be able to replace the packing step with a tool like CWM, which is already verified. This is important for me, since I want to make sure I am not doing something wrong and messing up the file when I pack it. Can someone please help? The original question stands; has anyone successfully put CWM on this platform, and if so please share the file(s) and procedure(s) with me.
Well I have had CWM on my n9005, which doesn't help, but have you tried on the Sprint forums? There's n900p CWM Recovery and a search brings up a number of threads to check.
One immediate thing that jumps out is it recommends using Odin 3.04 - maybe it doesn't work with other versions?
Journyman16 said:
Well I have had CWM on my n9005, which doesn't help, but have you tried on the Sprint forums? There's n900p CWM Recovery and a search brings up a number of threads to check.
One immediate thing that jumps out is it recommends using Odin 3.04 - maybe it doesn't work with other versions?
Click to expand...
Click to collapse
Thank you so much. I'll give it a try. I hoped for a more recent version of CWM. I just found out that I can use flashify to flash .img files; so I am gonna try that on my recovery.img file I just built. That may fulefill my requirement.
Thank you so much for the help.
I know I had a little trouble trying to find these specific recoveries due to goo.im being gone and the TWRP listing for the WIFI ONLY MODEL [SM-P600] not on their site. So I'm posting this to shorten your searches if this is for what you are searching.
All I did was use UNIFIED ANDROID TOOLKIT to flash the recovery via ODIN. But I'm going to attach phil's recovery file from the above toolkit if anyone wants it because it is hard to find for this model. Its the md5 file for use with ODIN. I think your best bet might just be to use the UNIFIED ANDROID TOOLKIT thread link above to do what you want with the device. It allows for flashing of TWRP or PHIL's. The TWRP file is named lt03wifiue so I didn't try it on mine, but it may work. But all that is up to you friend.
Not sure if this is the best place for this thread. I'm sure it will find it's right home.
Thanks.
I had to remove the .md5 extension on Phil's file only to get it to upload to XDA. So add that back.
TWRP works thanks was desperate
kooks05 said:
TWRP works thanks was desperate
Click to expand...
Click to collapse
No problem. I knew it was a pain to find something trust worthy. So I had to get it out there.
TWRP works without a hitch?