this is compiled form pure ClockWorkMod sources.
and i do a little modified.
now it's using the htc stock processbar and background.
use at you own risk.
i've already tested it, all function works as it should.
Please unlock your bootloader via htcdev.com
then use fastboot to flash this.
Code:
fastboot flash recovery recovery.img
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Downloads :
View attachment runnymede-cwm-recovery.zip
Has anyone had a play with this yet? Im reluctant due to no official word from Koush yet...
very nice work, now we just need someone to try flash the rom hehe
it works so why do we need koush for everything...... there are others who are just as capable. this along with chinese version work so i am happy. now try cappy rom lol
---------- Post added at 03:37 PM ---------- Previous post was at 03:19 PM ----------
flashed this recovery.img which is english and it works. just backing up my original rom now to flash cappys runnymede v1.1. excited as well. back up completed without a hitch and mounted usb storage in recovery. all seems fine guys for now
---------- Post added at 03:56 PM ---------- Previous post was at 03:37 PM ----------
did wipe data/factory reset which completed successfully and install zip from sdcard etc so i am happy with it for now
shingers5 said:
it works so why do we need koush for everything...... there are others who are just as capable. this along with chinese version work so i am happy. now try cappy rom lol
---------- Post added at 03:37 PM ---------- Previous post was at 03:19 PM ----------
flashed this recovery.img which is english and it works. just backing up my original rom now to flash cappys runnymede v1.1. excited as well. back up completed without a hitch and mounted usb storage in recovery. all seems fine guys for now
---------- Post added at 03:56 PM ---------- Previous post was at 03:37 PM ----------
did wipe data/factory reset which completed successfully and install zip from sdcard etc so i am happy with it for now
Click to expand...
Click to collapse
this is based on Koush's Open Sources ClockWorkMod Recovery, so indeed we need Koush. we should thank koush for his great work and contribution for this community. BTW. Thanks for confirming this is working.
tenfar said:
this is based on Koush's Open Sources ClockWorkMod Recovery, so indeed we need Koush. we should thank koush for his great work and contribution for this community. BTW. Thanks for confirming this is working.
Click to expand...
Click to collapse
nope i dint mean it like that mate. yea all of this wouldnt be possible without him but we shouldnt be reluctant to try it just cause he hasnt endorsed it. just cause you posted it dont mean it wont work ..................... as i can testify it works and quite well. i just done a full restore from back up and it went through flawlessly. thanks again to you and koush for his open sopurces.
shingers5 said:
nope i dint mean it like that mate. yea all of this wouldnt be possible without him but we shouldnt be reluctant to try it just cause he hasnt endorsed it. just cause you posted it dont mean it wont work ..................... as i can testify it works and quite well. i just done a full restore from back up and it went through flawlessly. thanks again to you and koush for his open sopurces.
Click to expand...
Click to collapse
Can i ask how you got S-OFF? On the HTCdev.com it doesn't have sensation XL listed
wwfc said:
Can i ask how you got S-OFF? On the HTCdev.com it doesn't have sensation XL listed
Click to expand...
Click to collapse
its there. i take it you mean unlock bootloader? s-off isnt available as yet from what i can see but from htc dev you can unlock ya bootloader. HTC sensation xl or runnymede(RUNNYMEDE) - same phone
shingers5 said:
its there. i take it you mean unlock bootloader? s-off isnt available as yet from what i can see but from htc dev you can unlock ya bootloader. HTC sensation xl or runnymede(RUNNYMEDE) - same phone
Click to expand...
Click to collapse
Hi all, on the htc dev website i cant see the sensation xl at all..... are you using the sensation xe htc sync?
+1,
Same.....no Sensation xl or runnymede found
Can someone write a Howto?
Or somebody have it uploadet to a mirror?
I think, there are some progs for download, to manage the unlock....
I have Rom 207, normally 407, so I wonder, if it is O2-Germany brandet....
Can I unlock my Bootloader too?
jammysunny said:
+1,
Same.....no Sensation xl or runnymede found
Can someone write a Howto?
Or somebody have it uploadet to a mirror?
I think, there are some progs for download, to manage the unlock....
I have Rom 207, normally 407, so I wonder, if it is O2-Germany brandet....
Can I unlock my Bootloader too?
Click to expand...
Click to collapse
you dont need to see it in the list. it did not show in the list does not mean it can not been unlocked. just follow the steps. you can unlock your phones bootloader if you can use fastboot command to get the identify token.
I have 207 in Softwareinfo, so, can I do it with this O2-Rom too?
Damn, I cant install JDK.....any help??
jammysunny said:
Damn, I cant install JDK.....any help??
Click to expand...
Click to collapse
can somebody upload a original recovery image file so can be flashed back?
---------- Post added at 08:28 AM ---------- Previous post was at 08:19 AM ----------
jammysunny said:
Damn, I cant install JDK.....any help??
Click to expand...
Click to collapse
first write down whats your problem?
Ok, sorry,
I wanted to unlock the bootloader, so I registered me on the page "htcdev.com", to do it....
But before unlocking, I wanted to check my Java and my SDK, so I installed my Java, but it couldnt be installed
And thats the base of the SDK, so my first step doesnt be positive....
Edit: I managed it, cool!!
I had a problem with my defy (I replaced a system file), and now it doesn't start into androdi, so I need to flash a custom recovery with RSD Lite.
..but I can't find an image file with only CWM.
Could you please share how did you recompile CWM?
Thanks in advance!
how to flash it in fastboot ?
Vry.I.Prsn said:
how to flash it in fastboot ?
Click to expand...
Click to collapse
Firstly I would suggest using the Paul O'Brein recovery from the MoDaCo site
http://android.modaco.com/topic/348973-clockworkmod-recovery-5027-unofficial-modaco-edition/
Also have you got the Fastboot tools on your computer, you will need these to be able to install CWM and they're part of the android sdk package. Once you have the fastboot tools, move the recovery.img to the folder where fastboot.exe is and open a command window (I take it your using windows... hold left shift button and then right click, in the options you will see 'open command prompt here') and from the command prompt type this
fastboot flash recovery r1-recovery-clockwork-5.0.2.7-modaco-runnymede.img (tip is to type r1 then hit tab to complete full line without typing it all)
This has all been explained in other threads...
I was bored today at work, so I've download and flashed this Recovery
My process was;
Stock
November time I unlocked the Bootloader
waited mainly due to lazyness
Today downloaded this Recovery
Flashed recovery via fastboot
Jobs a good 'un
Done a backup and waiting on RCMix3D Runny to download then install etc
No special tools or tricks of the trade, have had the SDK etc installed on my PC here since my G1 on launch day,, well soon after launch day anyway
[vertigo] said:
Firstly I would suggest using the Paul O'Brein recovery from the MoDaCo site
http://android.modaco.com/topic/348973-clockworkmod-recovery-5027-unofficial-modaco-edition/
Also have you got the Fastboot tools on your computer, you will need these to be able to install CWM and they're part of the android sdk package. Once you have the fastboot tools, move the recovery.img to the folder where fastboot.exe is and open a command window (I take it your using windows... hold left shift button and then right click, in the options you will see 'open command prompt here') and from the command prompt type this
fastboot flash recovery r1-recovery-clockwork-5.0.2.7-modaco-runnymede.img (tip is to type r1 then hit tab to complete full line without typing it all)
This has all been explained in other threads...
Click to expand...
Click to collapse
I just keep getting <waiting for device>
Related
Hi,
My device is Flex D958 had 4.4.2 Kitkat version software. I got right to the root Towelroot.apk and after Freedom Flex with TWRP recovery. TWRP recovery was working but the device did not boot. I wanted to open it up and ROM D955 Flashable. Sideload did not work and phone not opening Bootloader mode; write the bootloader text and was staying at a few points. Flashed in link ROM wit OTG cable flash card. The device has been opened but the IMEI is null writes. Although not entirely stable working fine, but not EFS. I want to send the device to the LG service, going to demand change of phone. But here are sold as D958, D955 is not sold.However, the text does not say rooted in the bootloader. What can we do? Or should I use the IMEI be solved or şlet me turn to D958 bootloader and system bla bla bla, service roads. Please help????
Border Force.
How did you miss all the warnings that nothing is working as intended with 4.4.2??????
And why in the world do you think LG is responsible for this?
I did the same thing I have the sprint flex 4.4 rooted did the freedom flex saw a guy do it in the video thought his phone had kit Kat too but I guess not anyway I can push via adb but nothing will flash and some how everything is wiped like the internal I can push files to sdcard and data and so on but when I try to flash the zips they are unable to open error comes up any one wanna blue my mind with the fix thanks guys
Is there a solution? Sorry my poor English and I do not understand some of what you say, using Google Translate. I from Turkey
Sent from my LG-D802 using XDA Free mobile app
border force said:
Is there a solution? Sorry my poor English and I do not understand some of what you say, using Google Translate. I from Turkey
Sent from my LG-D802 using XDA Free mobile app
Click to expand...
Click to collapse
just reread your OP. So your phone boots fine but imei, # etc not showing, correct?
Did you happen to backup efs with freedomflex or ioroot in the past?
Yes, phone boot fine but semi stability. IMEI null and Baseband version is unknown. I did get a EFS replacement with TWRP, but threw his memory erased flashable software. Flashed 4.2.2 TOT not working baseband and flashed 4.4.2 KDZ but baseband unknown. Using JB and KK Freedom Flex install TWRP or Cwm Reco but can not establish. Octoplus Box LG Tool with write imei, yet negative result. IMEI even when the phone is not fully stable. TWRP or Cwm is founded I think I can D958. How can we do? If it can 958 work fine again? IMEI solution? Sorry my poor English. Pls help????
Sent from my LG-D802 using XDA Free mobile app
border force said:
Yes, phone boot fine but semi stability. IMEI null and Baseband version is unknown. I did get a EFS replacement with TWRP, but threw his memory erased flashable software. Flashed 4.2.2 TOT not working baseband and flashed 4.4.2 KDZ but baseband unknown. Using JB and KK Freedom Flex install TWRP or Cwm Reco but can not establish. Octoplus Box LG Tool with write imei, yet negative result. IMEI even when the phone is not fully stable. TWRP or Cwm is founded I think I can D958. How can we do? If it can 958 work fine again? IMEI solution? Sorry my poor English. Pls help????
Sent from my LG-D802 using XDA Free mobile app
Click to expand...
Click to collapse
you have to have a efs backup in order to restore it. If you used ioroot in the past to root you should have a efs backup in the ioroot dir on your pc. If you have those, you can push them to your phone and flash.
PlayfulGod said:
you have to have a efs backup in order to restore it. If you used ioroot in the past to root you should have a efs backup in the ioroot dir on your pc. If you have those, you can push them to your phone and flash.
Click to expand...
Click to collapse
IORoot program does not work with me I'm doing with the device Towelroot.apk, I am setting up and you're then going to superuser. However, when I install Freedom Flex does not want root permission. I was able to establish the beginning of all these events. It also does not install TWRP because supersu permissions not working. You could set up TWRP using and it's in my hand D958 has Flashable.zip. After not matter, then you could have done without the phone IMEI. My sender service, guaranteed. Here you do not accept 955, accepting 958 variant.
Sorry sorry sorry my poor English. We do not fully agree, but thank you for your help I guess I could tell my troubles
Please,
PlayfulGod said:
How did you miss all the warnings that nothing is working as intended with 4.4.2??????
Click to expand...
Click to collapse
ive used your freedom flex but missed the warnings for ive been looking for this recovery files. now i bricked my lg g flex d958. i tried your cm11 for d 959, it updates then work up to the menus, but everytime it reboots. if you have cm11 for d958, it will be greatly appreciated. i maybe can help also in testing some of your program on my flex d958 in the future if you need but please let me out of this misery.
"Thank you very much, i know you only wants to help and its our fault when we make mistakes."
958 lg
my 958 3 days old is bricked and i think i did him a factory reset so he got nothing on him
yes i can get into download mode or to recovery but!!! my pc doesnt recognize he is pluged in
please solution please
and yes its happend afer i use freedom app
ohad129 said:
my 958 3 days old is bricked and i think i did him a factory reset so he got nothing on him
yes i can get into download mode or to recovery but!!! my pc doesnt recognize he is pluged in
please solution please
and yes its happend afer i use freedom app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2797190
Try that to flash using the kdz. Of it won't work point me to a working kdz for your phone and I'll try to throw together a zip you can flash in twrp.
Now not trying to be a jerk, but why in the hell did you ignore all the warnings and use the freedom flex app? Did you not believe the message saying it will brick you?
Cause im am real jerk i admit it
if my device not recognize i get your device is not connected how can i use that app?
Sent from my Nexus 5 using Tapatalk
---------- Post added at 06:19 PM ---------- Previous post was at 06:03 PM ----------
to choose cdma i know but he got some choices?
also when i got to choose version? what shoult i choose?
normal flash ? or cse flash?
please let me know!!!!!
thx in advance
ohad129 said:
Cause im am real jerk i admit it
if my device not recognize i get your device is not connected how can i use that app?
Sent from my Nexus 5 using Tapatalk
---------- Post added at 06:19 PM ---------- Previous post was at 06:03 PM ----------
to choose cdma i know but he got some choices?
also when i got to choose version? what shoult i choose?
normal flash ? or cse flash?
please let me know!!!!!
thx in advance
Click to expand...
Click to collapse
Just run it exactly as it's shown in the picture. Make sure drivers are installed, you're in download mode and hopefully your computer recognizes it. If not try rebooting pc, different cable and different computer.
Normal flash will not factory reset phone. Cse flash will reset phone and wipe internal storage. I'd try normal and if it didn't work then cse.
You mean if i download the hongkong version kdz thats it also the version ?
Sent from my Nexus 5 using Tapatalk
ok no prob
temme one thing. can you flash twrp recovery? if you can boot to recovery i.e. twrp, i can upload for you the backup of my D958 Rom which you can restore and everything should be fine. but i'm not on kitkat i'm on rooted 4.2.2
jacktackle said:
ok no prob
temme one thing. can you flash twrp recovery? if you can boot to recovery i.e. twrp, i can upload for you the backup of my D958 Rom which you can restore and everything should be fine. but i'm not on kitkat i'm on rooted 4.2.2
Click to expand...
Click to collapse
Great for me thx im in twrp but device isnt recognized by pc so how can i can upload it inside? Please account me as noob
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 5 using Tapatalk
you can use USB OTG cable. if you do not have one try and get one.
twrp reads OTG usb. you can copy and paste the backup folder on the internal storage.
Ok i will and then you will send me a file? Or should i download it from the wild? I bought him in hong kong so should i download hong kong version? They got 2 should i download the latest?
Sent from my Nexus 5 using Tapatalk
I got a otg cable? How to do it please help!!!
You write backup ? So which file is that zip or tgz?
Sent from my Nexus 5 using Tapatalk
---------- Post added at 03:28 PM ---------- Previous post was at 03:00 PM ----------
Any commend line i need to type? I got on thar disk on key the rom !
Sent from my Nexus 5 using Tapatalk
---------- Post added at 03:37 PM ---------- Previous post was at 03:28 PM ----------
Ok my device see the hong kong rom but it fail to upload any idea or i need anothet file to rescue my device please help
Sent from my Nexus 5 using Tapatalk
---------- Post added at 04:12 PM ---------- Previous post was at 03:37 PM ----------
kintwofan said:
http://forum.xda-developers.com/showthread.php?t=2797190
Try that to flash using the kdz. Of it won't work point me to a working kdz for your phone and I'll try to throw together a zip you can flash in twrp.
Now not trying to be a jerk, but why in the hell did you ignore all the warnings and use the freedom flex app? Did you not believe the message saying it will brick you?
Click to expand...
Click to collapse
i got an OTG cable and try to flash the kdz file but its looks like its to fast then i got the fail also try to flash zip file and the same too
which file i need to try?
my device its hkg type so should i try the latest stock firmware or something else?
thx in advance
Hi, I hope I post this in the right place. Anyway, as the title suggests, I want to get back stock recovery on my Nexus 6 without getting back the entire system image. I currently have TWRP as a recovery and I want to be able to receive OTA updates but I would need to uninstall BusyBox, which TWRP uses. The only thing that is 'custom' right now is the recovery and that's all I want to replace because I've heard that if I flash the entire system image, I lose data. I haven't been successful in finding the exact guide or support I need so I am posting my own thread. Sorry if it's in the wrong place.
You would download the stock image, extract recovery.img from that, boot phone into the bootloader and using a computer with the Android SDK installed, use the command fastboot to flash the recovery, so: fastboot flash recovery recovery.img
There's guides here on how to do this.
RMarkwald said:
You would download the stock image, extract recovery.img from that, boot phone into the bootloader and using a computer with the Android SDK installed, use the command fastboot to flash the recovery, so: fastboot flash recovery recovery.img
There's guides here on how to do this.
Click to expand...
Click to collapse
I have Android SDK but I have no idea how to do it. I don't suppose you have a link? If not, it's alright. Thank you for the quick response.
I have found guides on how to do it, but I can't get them to work. Haven't seen one using Android SDK.
Are you rooted?
Sent from my Nexus 6 using Tapatalk
---------- Post added at 07:51 AM ---------- Previous post was at 07:47 AM ----------
Gotta be with busy box, twrp. Flashifly should do the job. Strangely I've go a update alert on stock rooted ROM with twrp.
Official Team Bliss Flo/Deb/v410 Maintainer
Sent from my Nexus 6 using Tapatalk
713brianp27 said:
Are you rooted?
Sent from my Nexus 6 using Tapatalk
---------- Post added at 07:51 AM ---------- Previous post was at 07:47 AM ----------
Gotta be with busy box, twrp. Flashifly should do the job. Strangely I've go a update alert on stock rooted ROM with twrp.
Official Team Bliss Flo/Deb/v410 Maintainer
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yes I am.
So, I flashed the stock recovery of Android 5.0.1 and when I try to boot into recovery, I get an Android laying down, chest open with a red caution sign. I think I may have downloaded the wrong version. I probably have Android 5.1 not 5.0.1
Flashifly app does fine job on boot&recovery. Don't see the need for fastboot. Hate wiring up to a computer just for an image. It'll flash it then boot you to it. Bam done
Sent from my Nexus 6 using Tapatalk
You'll not be able to flash teh update because youa re rooted. You will need to flash recovery.img and system.img and boot.img to get back to 100% stock. You will recieve OTA then, though you may aswell download latest version now so no need to update.
---------- Post added at 03:59 PM ---------- Previous post was at 03:58 PM ----------
713brianp27 said:
Flashifly app does fine job on boot&recovery. Don't see the need for fastboot. Hate wiring up to a computer just for an image. It'll flash it then boot you to it. Bam done
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Flashify doesn't flash system.images. You need to do that to flash back to stock.
Flashifly most certainly does. Exactly where is your info coming from.
Sent from my Nexus 6 using Tapatalk
---------- Post added at 09:07 AM ---------- Previous post was at 09:07 AM ----------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 6 using Tapatalk
713brianp27 said:
Flashifly most certainly does. Exactly where is your info coming from.
Sent from my Nexus 6 using Tapatalk
---------- Post added at 09:07 AM ---------- Previous post was at 09:07 AM ----------
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
My info is coming from the fact I have flashify installed for many yars and now it is also coming from your screenshot, which also confirms it cannot flash system images.
Screen shows two images?! Your boot and recovery ARE images. What is the point of the app otherwise?
http://highonandroid.com/android-ap...n-rooted-android-with-flashify-app-root-apps/
Sent from my Nexus 6 using Tapatalk
713brianp27 said:
Screen shows two images?! Your boot and recovery ARE images. What is the point of the app otherwise?
http://highonandroid.com/android-ap...n-rooted-android-with-flashify-app-root-apps/
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
#
I think you're misreading my post. I didn't say it cannot flash images. I said it cannot flash System Images.
danarama said:
#
I think you're misreading my post. I didn't say it cannot flash images. I said it cannot flash System Images.
Click to expand...
Click to collapse
I never said it could flash the system.img
The thread is about recovery. Cut and dry. You bring in a fact I'm aware of. But no one is talking about the system.img . it would be system image, not system images which could confuse , using it plural implies reference to images in the system (partition). Anyway. You can flash your stock recovery.img with app. Thread question solved. And folks he's right, can't flash system image.
Sent from my Nexus 6 using Tapatalk
713brianp27 said:
I never said it could flash the system.img
The thread is about recovery. Cut and dry.
Click to expand...
Click to collapse
No it is not. Read between the lines. The thread is about being able to accept OTA updates. Flashing stock recovery is what the OP has guessed is required to do this (he is wrong)
713brianp27 said:
You bring in a fact I'm aware of.
Click to expand...
Click to collapse
Really? I said it cannot flash system images twice and you still said it could. Maybe you are aware of it, but your reading misses things. I'll give you the benefit of the doubt.
713brianp27 said:
But no one is talking about the system.img
Click to expand...
Click to collapse
I AM!!! Because that is the resolution to this thread.
713brianp27 said:
it would be system image, not system images which could confuse , using it plural implies reference to images in the system (partition).
Click to expand...
Click to collapse
What, you flash one image and then it explodes, so you can't flash any more? You can flash multiple recovery images. I use plural because the English language allows for it. And Yes, System images are the System partition. Not sure I'm grasping your point.
713brianp27 said:
Anyway. You can flash your stock recovery.img with app
Click to expand...
Click to collapse
Great! Though no help here.
713brianp27 said:
Thread question solved.
Click to expand...
Click to collapse
Yes, by using fastboot, which was why I posted about flashify not being able to flash system images. "Don't see a need for fastboot" - Well, there is a need.
Thread title"Getting back stock recovery". Easy. Answered. She want the ota. Not a system.img. Yhey get recovery. Should they get an alert. OTA.
Here is my point. 1) what's the title, answered.
2)you bring up "can't ..." When NOBODY EVER said flash system.img with any app, fastboot, or any other means. Intent is get it via carrier download---
3) How in the world of reality do you flash something that is coming through the carrier update push , as far as I know they don't leave a copy behind
4) Stick to topic. Title... Simple. I can flash stock recovery now, and reflash twrp. So why the "need". Why bring up system image(s). Which can be packaged and flashed in custom recovery. I've got an ota notice running stock root so the only thing I would of lacked was ... Yes correct recovery
I apologize for entertaining and debating. I am going to make an exit. Good day
Sent from my Nexus 6 using Tapatalk
713brianp27 said:
Thread title"Getting back stock recovery". Easy. Answered. She want the ota. Not a system.img. Yhey get recovery. Should they get an alert. OTA.
Here is my point. 1) what's the title, answered.
2)you bring up "can't ..." When NOBODY EVER said flash system.img with any app, fastboot, or any other means. Intent is get it via carrier download---
3) How in the world of reality do you flash something that is coming through the carrier update push , as far as I know they don't leave a copy behind
4) Stick to topic. Title... Simple. I can flash stock recovery now, and reflash twrp. So why the "need". Why bring up system image(s). Which can be packaged and flashed in custom recovery. I've got an ota notice running stock root so the only thing I would of lacked was ... Yes correct recovery
I apologize for entertaining and debating. I am going to make an exit. Good day
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Look, all I wanted to do was help the OP get what they want and identify the need for using fastboot.
The fact that you either didn't read the thread properly or don't have the technical understanding of OTA to answer the question effectively is of no concern. You can argue what you want, but flashify won't help here. Reading the title of a thread is not enough, you should read the full opening post first. You can be forgiven for not having the technical understanding needed to resolve the issue. But you shouldn't keep going on when someone points out that your answer won't help.
In regards to your very last point. Getting notification is not the same as getting the ota. Yes you need stock recovery, but also you must have 100% stock android. No root. Must be never rooted.. I can tell you're a noob by not knowing this and again, that is fine. What is not fine though, is your attitude and refusing to believe you are wrong. It's not the first time you've been like this either. I've seen it before.. I don't really care what you think you know though to be honest.
@Prowler1000, the *ONLY* way you will successfully get an OTA officially in the future is by flashing the system.img first.
You cannot simply have a stock recovery or use any other unroot methods. You must have a clean, untouched rom and kernel, never rooted.. Any change, even if just one letter in a text file of the rom will be enough to make the official OTA flash fail, this i promise you. This is why you must flash a system.image.
Actually on a ROM I built in buildbox. And know my way around. But think what you want. Said bye once. Troll on. Your blocked so I hear no more
Sent from my Nexus 6 using Tapatalk
713brianp27 said:
Actually on a ROM I built in buildbox. And know my way around. But think what you want. Said bye once. Troll on. Your blocked so I hear no more
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Haha. You're priceless. Luckily, anyone reading this thread will see your true qualities.
danarama said:
No it is not. Read between the lines. The thread is about being able to accept OTA updates. Flashing stock recovery is what the OP has guessed is required to do this (he is wrong)
Click to expand...
Click to collapse
No, I just needed to get rid of TWRP so I could get rid of BusyBox. That is all.
Edit: I was hoping by getting rid of BusyBox, I could update without having to flash a system.img so that I don't have to wipe my phone. But I guess that is out of the picture. I will just flash M, rather then waiting for the OTA.
Prowler1000 said:
No, I just needed to get rid of TWRP so I could get rid of BusyBox. That is all.
Edit: I was hoping by getting rid of BusyBox, I could update without having to flash a system.img so that I don't have to wipe my phone. But I guess that is out of the picture. I will just flash M, rather then waiting for the OTA.
Click to expand...
Click to collapse
What you are saying is you want to get rid of TWRP so you can get rid of busybox (TWRP does not need busybox by the way) and that getting rid of busy box will enable you to get an Update.
What I am saying is that is not enough. Root is preventing you getting the update. You *must* flash the system.img to clean your ROM to be able to accept future updates.
However, for info, flashing a system.img does NOT wipe your phone. system.img goes in the /system partition only. It is the ROM. all your data is in the data partition. If you just flash the system.img, recovery.img and boot.img, you will be stock enough to take updates in the future. If you flash the full factory image (which includes all the indivudual images I mentioned, plus cache.img, userdata.img, radio.img, bootloader.img) then that WILL wipe your phone, but you do not need to do that.
If your plan is to stay rooted in the future, the best thing is to keep TWRP and just flash the system.img and boot.img when you ware ready to update. OTA's are more hassle than benefit anyway, and you cant take them if you want to stay rooted. But once rooted on a stock rom, you can never unroot without flashign that system.img (at least not to the point where an OTA will flash successfully
danarama said:
What you are saying is you want to get rid of TWRP so you can get rid of busybox (TWRP does not need busybox by the way) and that getting rid of busy box will enable you to get an Update.
What I am saying is that is not enough. Root is preventing you getting the update. You *must* flash the system.img to clean your ROM to be able to accept future updates.
However, for info, flashing a system.img does NOT wipe your phone. system.img goes in the /system partition only. It is the ROM. all your data is in the data partition. If you just flash the system.img, recovery.img and boot.img, you will be stock enough to take updates in the future. If you flash the full factory image (which includes all the indivudual images I mentioned, plus cache.img, userdata.img, radio.img, bootloader.img) then that WILL wipe your phone, but you do not need to do that.
If your plan is to stay rooted in the future, the best thing is to keep TWRP and just flash the system.img and boot.img when you ware ready to update. OTA's are more hassle than benefit anyway, and you cant take them if you want to stay rooted. But once rooted on a stock rom, you can never unroot without flashign that system.img (at least not to the point where an OTA will flash successfully
Click to expand...
Click to collapse
But I can manually flash the new update, right?
Here're the 7zip-ed stock boot, recovery and system images for the Cherry Mobile One G1:
6.0 (MRA58Y):
Boot: here
*SHA1: 577943CC98CFA242BE149418A9551063CBCB7704
Recovery: here
*SHA1: FDED2C995FDFAB4B9CC1A3A76F5B78F962D730A5
System: here
*SHA1: 7C31848ABE4966AB7BB0867AEEC314DF6895E568
5.1.1 (LUZ59Q):
Boot: here
*SHA1: 260ABCE487CFA01655D5B9E292FDB0E6EA4484EE
Recovery: here
*SHA1: 3902D668BC53E68A919972310AF36A429842AA1C
System: here
*SHA1: B7D4C903BB3D5E7A2E462BDF83C966BEFB4E3B53
5.1.1 (LUZ59M):
Boot: here
*SHA1: 86DF519A78BDDB3A7010EB999CAE64C72AB5E8A0
Recovery: here
*SHA1: 16072C9FD1777FC4264094B367422A3BC47013FE
System: here
*SHA1: 900A86BD863E5998AC0BF989B1DDB1896B4DEC96
MMB29K from MRA58Y:
here
MRA58Y from LUZ59Q:
here
LUZ59Q from LUZ59M:
here
LUZ59M from LUZ59J:
here
Disclaimer: Flash at your own risk as usual.
*SHA1 hashes are for the UNCOMPRESSED files and not the 7z files...
Notes/FAQ:
1.) I compressed them using 7zip since I'll be uploading extremely large files if I didn't. SHA1 hashes for boot and recovery matches those in the install-recovery.sh system file.
2.) The commands for flashing are as follows:
Boot: fastboot flash boot boot.img
Recovery: fastboot flash recovery recovery.img
System: fastboot flash system system.img
*replace boot.img, recovery.img and system.img with their respective filenames
**how to obtain the fastboot executables and drivers are explained in a separate thread
3.) The system.img provided above are stock and NOT ROOTED. If you want to go completely stock, just flash ALL the images above.
4.) These are not meant for UPGRADING. Upgrades usually have bootloader updates in them which might be required.
General mobile
My stock version is LUZ59R, can I flash these filmwares on the General mobile android one 4G?
thanks
Saphire007 said:
My stock version is LUZ59R, can I flash these filmwares on the General mobile android one 4G?
thanks
Click to expand...
Click to collapse
I don't know. Might work but then the OTA's you'll receive might be the Cherry Mobile ones instead of General Mobile's.
intersectRaven said:
I don't know. Might work but then the OTA's you'll receive might be the Cherry Mobile ones instead of General Mobile's.
Click to expand...
Click to collapse
Thanks, I guess I won't take the risk
Today I decided flashing the full firmware from Wileyfox Cyanogen OS 12.1 and played with it a little and decided that the G1 stock rom is better for me personally. So, I tried going back to the stock rom by flashing OTA files given above, but to no avail. It only gave me black screen. I was lucky that I was still able to boot into bootloader and reflash the Wileyfox Rom. So I was wondering if somebody could please pull the full stock rom files from their G1. I really wanted to go back to stock.
The above-posted files ARE the stock images for the G1...
rho57 said:
Today I decided flashing the full firmware from Wileyfox Cyanogen OS 12.1 and played with it a little and decided that the G1 stock rom is better for me personally. So, I tried going back to the stock rom by flashing OTA files given above, but to no avail. It only gave me black screen. I was lucky that I was still able to boot into bootloader and reflash the Wileyfox Rom. So I was wondering if somebody could please pull the full stock rom files from their G1. I really wanted to go back to stock.
Click to expand...
Click to collapse
rho57 said:
Today I decided flashing the full firmware from Wileyfox Cyanogen OS 12.1 and played with it a little and decided that the G1 stock rom is better for me personally. So, I tried going back to the stock rom by flashing OTA files given above, but to no avail. It only gave me black screen. I was lucky that I was still able to boot into bootloader and reflash the Wileyfox Rom. So I was wondering if somebody could please pull the full stock rom files from their G1. I really wanted to go back to stock.
Click to expand...
Click to collapse
This for imobile IQ II(same as G1)
To return to stock rom from CM12.1(wiley Swift)
1.Download ReTurn_IQ_Rom.rar from here and extract to pc destop.
https://drive.google.com/open?id=0BznGujNFQUzsRUctWlNPelV6NDQ
2.Unlock bootloader of your device again(after flashed your device with CM12.1,bootloader may be turn to relock)
3.boot your device to bootloader and connect to pc
4. double click at "3_return_IQ_rom.bat"
5. After first boot , connect your device via wifi to get ota-update from google ,immediately
Beach_Head said:
The above-posted files ARE the stock images for the G1...
Click to expand...
Click to collapse
They are stock images, I know. But those don't include stock images from bootloader and other partitions that were changed during the flashing.
---------- Post added at 07:49 AM ---------- Previous post was at 07:46 AM ----------
mrd.macdonald said:
This for imobile IQ II(same as G1)
To return to stock rom from CM12.1(wiley Swift)
1.Download ReTurn_IQ_Rom.rar from here and extract to pc destop.
https://drive.google.com/open?id=0BznGujNFQUzsRUctWlNPelV6NDQ
2.Unlock bootloader of your device again(after flashed your device with CM12.1,bootloader may be turn to relock)
3.boot your device to bootloader and connect to pc
4. double click at "3_return_IQ_rom.bat"
5. After first boot , connect your device via wifi to get ota-update from google ,immediately
Click to expand...
Click to collapse
Thanks, but before I do another flash, was this tested to work for the G1 already? I mean hypothetically it should work considering that they're all Android One devices, but has anybody actually tried returning to stock A1 rom from Cyanogen OS using this on the G1?
rho57 said:
They are stock images, I know. But those don't include stock images from bootloader and other partitions that were changed during the flashing.
---------- Post added at 07:49 AM ---------- Previous post was at 07:46 AM ----------
Thanks, but before I do another flash, was this tested to work for the G1 already? I mean hypothetically it should work considering that they're all Android One devices, but has anybody actually tried returning to stock A1 rom from Cyanogen OS using this on the G1?
Click to expand...
Click to collapse
If you're just going to go back to the stock you had before going to a CyanogenMod ROM you don't need those firmware files since the CyanogenMod ROMs don't modify those. You just need to flash the correct version that matches your original one.
rho57 said:
Thanks, but before I do another flash, was this tested to work for the G1 already? I mean hypothetically it should work considering that they're all Android One devices, but has anybody actually tried returning to stock A1 rom from Cyanogen OS using this on the G1?
Click to expand...
Click to collapse
The Cyanogen OS .bat installer flashes the other partitions too. Best to wait for a full G1 dump.
arvinquilao said:
The Cyanogen OS .bat installer flashes the other partitions too. Best to wait for a full G1 dump.
Click to expand...
Click to collapse
Exactly. What I was looking for was the full G1 dump.
---------- Post added at 03:28 PM ---------- Previous post was at 03:24 PM ----------
intersectRaven said:
If you're just going to go back to the stock you had before going to a CyanogenMod ROM you don't need those firmware files since the CyanogenMod ROMs don't modify those. You just need to flash the correct version that matches your original one.
Click to expand...
Click to collapse
You might be confusing CyanogenMod, which is a custom rom, from Cyanogen OS which is the stock ROM of Wileyfox. If you've tried flashing the Cyanogen OS from needrom, you should've known that it doesn't just flash boot, system, and recovery, but other partitions such as radio and fastboot as well. Thanks for the insight anyway. I'll just wait for someone to release a full dump from the G1.
rho57 said:
Exactly. What I was looking for was the full G1 dump.
---------- Post added at 03:28 PM ---------- Previous post was at 03:24 PM ----------
You might be confusing CyanogenMod, which is a custom rom, from Cyanogen OS which is the stock ROM of Wileyfox. If you've tried flashing the Cyanogen OS from needrom, you should've known that it doesn't just flash boot, system, and recovery, but other partitions such as radio and fastboot as well. Thanks for the insight anyway. I'll just wait for someone to release a full dump from the G1.
Click to expand...
Click to collapse
I see...still, the full dump is already available. If you need the other partitions, the OTA has the bootloader, radio, etc.
intersectRaven said:
I see...still, the full dump is already available. If you need the other partitions, the OTA has the bootloader, radio, etc.
Click to expand...
Click to collapse
Nice, I didn't bother checking the OTA zip file until now. Indeed, the other partitions are present. I don't have a G1 yet, but thanks for the upload.
Exactly my point...
Perhaps he was on an older build...
intersectRaven said:
If you're just going to go back to the stock you had before going to a CyanogenMod ROM you don't need those firmware files since the CyanogenMod ROMs don't modify those. You just need to flash the correct version that matches your original one.
Click to expand...
Click to collapse
---------- Post added at 10:55 PM ---------- Previous post was at 10:51 PM ----------
Okay. Sorry for the confusion...
rho57 said:
Exactly. What I was looking for was the full G1 dump.
---------- Post added at 03:28 PM ---------- Previous post was at 03:24 PM ----------
You might be confusing CyanogenMod, which is a custom rom, from Cyanogen OS which is the stock ROM of Wileyfox. If you've tried flashing the Cyanogen OS from needrom, you should've known that it doesn't just flash boot, system, and recovery, but other partitions such as radio and fastboot as well. Thanks for the insight anyway. I'll just wait for someone to release a full dump from the G1.
Click to expand...
Click to collapse
intersectRaven said:
I see...still, the full dump is already available. If you need the other partitions, the OTA has the bootloader, radio, etc.
Click to expand...
Click to collapse
Please share G1's full dump .
Like intersectRaven already said, the full dump is already available.
The stock images are posted and the radios, etc. are in the the OTA files...
mrd.macdonald said:
Please share G1's full dump .
Click to expand...
Click to collapse
Beach_Head said:
Like intersectRaven already said, the full dump is already available.
The stock images are posted and the radios, etc. are in the the OTA files...
Click to expand...
Click to collapse
This partitions are not present in ota files,
splash , DDR , abootbak , hypbak , rpmbak , sbl1bak , splash , tzbak
Where to find it ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mrd.macdonald said:
This partitions are not present in ota files,
splash , DDR , abootbak , hypbak , rpmbak , sbl1bak , splash , tzbak
Where to find it ?
Click to expand...
Click to collapse
I won't be providing those as they're unimportant to restoring to a functioning stock boot.
Splash -> Why in heaven's name did you overwrite this?! Anyways, this is just for the spash screen on startup so not important.
*bak partitions -> These contains original boot, modem, etc. images from the factory. They're usually only used when the original fails since it's catastrophic when you can't load RPM or the like.
DDR -> This just contains zero data. Usually reformatted upon OTA since it has something to do with memory retraining. (my guess is to track "bad" memory)
LOL!
intersectRaven said:
Splash -> Why in heaven's name did you overwrite this?! Anyways, this is just for the spash screen on startup so not important.
Click to expand...
Click to collapse
I don't know why you even answered this guy...
Hi so I've spent a good deal of the morning attempting to finally fix this phone, a couple years ago I removed all OS from it and no backup but I still have TWRP.
The phone is tampered/unlocked.
Hboot is 1.54.0000
I tried loading one of the latest ROMS from here via side loading - http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
I used this guide - http://htc-one.wonderhowto.com/how-to/fix-soft-bricked-htc-one-by-flashing-new-rom-via-adb-0154361/
Unfortunately once the sideload is complete I get an error E: Zio file is corrupt, I was wondering if anyone knows what I'm doing wrong? Can attempt to provide more information if required.
Purdy8TV said:
Hi so I've spent a good deal of the morning attempting to finally fix this phone, a couple years ago I removed all OS from it and no backup but I still have TWRP.
The phone is tampered/unlocked.
Hboot is 1.54.0000
I tried loading one of the latest ROMS from here via side loading - http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
I used this guide - http://htc-one.wonderhowto.com/how-to/fix-soft-bricked-htc-one-by-flashing-new-rom-via-adb-0154361/
Unfortunately once the sideload is complete I get an error E: Zio file is corrupt, I was wondering if anyone knows what I'm doing wrong? Can attempt to provide more information if required.
Click to expand...
Click to collapse
What recovery version do you have? Try flashing newest TWRP and give it a go
donkeykong1 said:
What recovery version do you have? Try flashing newest TWRP and give it a go
Click to expand...
Click to collapse
Hey thanks for the reply
This is the ROM I downloaded https://www.androidfilehost.com/?fid=95916177934554130
My recovery version is v2.6.0.1 for TWRP, should I upgrade?
You can't flash that via recovery. That's a RUU, and your phone must be in RUU mode and you flash it via recovery. Also, you're on very old firmware, so you need to flash all firmwares before that one. My suggestikn is to flash the latest recovery, and then flash a custom ROM. You can find custom ROMs on M7 android development thread
donkeykong1 said:
You can't flash that via recovery. That's a RUU, and your phone must be in RUU mode and you flash it via recovery. Also, you're on very old firmware, so you need to flash all firmwares before that one. My suggestikn is to flash the latest recovery, and then flash a custom ROM. You can find custom ROMs on M7 android development thread
Click to expand...
Click to collapse
Ah that would explain it lol, sadly very inexperienced with this.
Would there be a stock rom or just choose the one close to stock? (As in HTC sense one)
Purdy8TV said:
Ah that would explain it lol, sadly very inexperienced with this.
Would there be a stock rom or just choose the one close to stock? (As in HTC sense one)
Click to expand...
Click to collapse
I think there should be a stock rooted ROM, but you can flash pretty much any ROM from there. Most of them are stockish looking
donkeykong1 said:
I think there should be a stock rooted ROM, but you can flash pretty much any ROM from there. Most of them are stockish looking
Click to expand...
Click to collapse
Hey thanks very much for your speedy replies
Would this be okay then - http://forum.xda-developers.com/htc-one/development/rom-google-play-edition-lollipop-v1-00-t2963927 ?
Also do I just sideload it as I attempted previously once TWRP is updated?
Purdy8TV said:
Hey thanks very much for your speedy replies
Would this be okay then - http://forum.xda-developers.com/htc-one/development/rom-google-play-edition-lollipop-v1-00-t2963927 ?
Also do I just sideload it as I attempted previously once TWRP is updated?
Click to expand...
Click to collapse
Of all sense TOMs out there, you picked a GPE [emoji4] that's not Sense, but it will work.
New recoveries have MTP option, so you don't need sideload. Just mount MTP, and move your zip to your phone
donkeykong1 said:
Of all sense TOMs out there, you picked a GPE [emoji4] that's not Sense, but it will work.
New recoveries have MTP option, so you don't need sideload. Just mount MTP, and move your zip to your phone
Click to expand...
Click to collapse
Haha yeah, I did decide I actually preferred closer to stock android after using my Z3
I don't really know how to do that, will side loading still be okay? (I assumed this was my only option as I literally have no OS on my phone and just get stuck at the HTC loading screen when I turn phone on normally)
Purdy8TV said:
Haha yeah, I did decide I actually preferred closer to stock android after using my Z3
I don't really know how to do that, will side loading still be okay? (I assumed this was my only option as I literally have no OS on my phone and just get stuck at the HTC loading screen when I turn phone on normally)
Click to expand...
Click to collapse
MTP is much easier than sideload, and newer TWRP have it. You go into recovery (updated) and you will see "mount MTP" option. Click that, and your phone will show up on your PC. After that it's just drag and drop, but sideload will work too I think
donkeykong1 said:
MTP is much easier than sideload, and newer TWRP have it. You go into recovery (updated) and you will see "mount MTP" option. Click that, and your phone will show up on your PC. After that it's just drag and drop, but sideload will work too I think
Click to expand...
Click to collapse
Hmm
I can just see 'Mount' on the main TWRP page, then I go into that and see Cache/Data/devlog/System/USB OTG as check boxes and then just disable MTP button at the bottom.
Nothing showing on my macbook (not sure if that makes a difference as my w10 pc could not recognise the phone at all)
Purdy8TV said:
Hmm
I can just see 'Mount' on the main TWRP page, then I go into that and see Cache/Data/devlog/System/USB OTG as check boxes and then just disable MTP button at the bottom.
Nothing showing on my macbook (not sure if that makes a difference as my w10 pc could not recognise the phone at all)
Click to expand...
Click to collapse
Disable MTP is the one. Click it twice, and you're good to go
donkeykong1 said:
Disable MTP is the one. Click it twice, and you're good to go
Click to expand...
Click to collapse
Not showing up as a removable storage
Purdy8TV said:
Not showing up as a removable storage
Click to expand...
Click to collapse
Weird... Then go with sideload
donkeykong1 said:
Weird... Then go with sideload
Click to expand...
Click to collapse
Okay so I tried side loading, downloaded the google plus ROM from the link I posted, zipped it up and ended up getting this error.
Purdy8TV said:
Okay so I tried side loading, downloaded the google plus ROM from the link I posted, zipped it up and ended up getting this error.
Click to expand...
Click to collapse
That error means your adb tool is not working properly. At least that was the case on my PC. Can you try it on your windows machine?
donkeykong1 said:
That error means your adb tool is not working properly. At least that was the case on my PC. Can you try it on your windows machine?
Click to expand...
Click to collapse
Yeah I'll go give it another go on it.
It wouldn't be anything to do with the fact my device is tampered? (S Off I think?) Do I need something extra other than just the one link in the ROM I said i chose?
Purdy8TV said:
Yeah I'll go give it another go on it.
It wouldn't be anything to do with the fact my device is tampered? (S Off I think?) Do I need something extra other than just the one link in the ROM I said i chose?
Click to expand...
Click to collapse
You're s-off??? Go to your bootlader and confirm that please
donkeykong1 said:
You're s-off??? Go to your bootlader and confirm that please
Click to expand...
Click to collapse
Talking out my arse I'm S-ON lol, thought tampered meant S OFF lol, apologies
donkeykong1 said:
You're s-off??? Go to your bootlader and confirm that please
Click to expand...
Click to collapse
Okay so windows can detect the device it seems!
I see this, do I just delete the sideload.zip and then drag and drop the ROM I downloaded ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Phone info:
SM-N920V
Android 6.0.1
Kernel 3.10.61
Build Number MMB29K.N920VV
I continue to have shut down issues, app has stopped working, reboots. I factory reset last night and after that I have an !...and the android guy is laying in his side under it. This happened on my last phone so I was given a replacement. I obviously have a corrupt file that is causing it. Any idea how to truly get back to factory wiped and fresh start with a happy android guy?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Are you able to get into recovery or download mode?
yes
yes I can get into recovery
MarkinCCAZ said:
yes I can get into recovery
Click to expand...
Click to collapse
Follow this guide here since that's a Verizon phone..
http://forum.xda-developers.com/ver.../downgrade-to-lollipop-5-1-1-verizon-t3368250
MrMike2182 said:
Follow this guide here since that's a Verizon phone..
http://forum.xda-developers.com/ver.../downgrade-to-lollipop-5-1-1-verizon-t3368250
Click to expand...
Click to collapse
Thank you MrMike - went through that successfully. Still have a sick android though. Poor guys is laying on his back with his stomach open and parts coming out. How is it possible to step back to a different operating system and still have problems? Have you seen the symbol that I posted above before?
MarkinCCAZ said:
Thank you MrMike - went through that successfully. Still have a sick android though. Poor guys is laying on his back with his stomach open and parts coming out. How is it possible to step back to a different operating system and still have problems? Have you seen the symbol that I posted above before?
Click to expand...
Click to collapse
After looking at your picture I'm wondering if you have a fake phone or something because there is no N920VVRS2BPF2 firmware that I have seen before.. Can you take a picture of the front of your phone so I can see the bezels?
Even Google cannot find that firmware number...
MrMike2182 said:
After looking at your picture I'm wondering if you have a fake phone or something because there is no N920VVRS2BPF2 firmware that I have seen before.. Can you take a picture of the front of your phone so I can see the bezels?
Even Google cannot find that firmware number...
Click to expand...
Click to collapse
Here is a pick.
I just got this phone last week, it was fine and operating perfectly. After getting apps downloaded and set up like my last phone, S6, I noticed it started to reboot itself and that apps would shut down. That's when I did a factory reset and saw the droid guy sideways. So some app, document or software download caused it to my knowledge.
where did you buy that from?
---------- Post added at 06:06 PM ---------- Previous post was at 05:58 PM ----------
MarkinCCAZ said:
Here is a pick.
I just got this phone last week, it was fine and operating perfectly. After getting apps downloaded and set up like my last phone, S6, I noticed it started to reboot itself and that apps would shut down. That's when I did a factory reset and saw the droid guy sideways. So some app, document or software download caused it to my knowledge.
Click to expand...
Click to collapse
Alright let's try this.. Download the firmware from here or wherever you want and then extract them so you'll be able to see each of the files modem, bootloader, recovery etc etc and then use Odin to put each file in the respective slots individually so they flash that way.. You may even need to use a PIT too so it reflashes the partitions..
http://forum.xda-developers.com/ver...mware-firmware-kernel-modem-recovery-t3214560
MrMike2182 said:
where did you buy that from?
---------- Post added at 06:06 PM ---------- Previous post was at 05:58 PM ----------
Alright let's try this.. Download the firmware from here or wherever you want and then extract them so you'll be able to see each of the files modem, bootloader, recovery etc etc and then use Odin to put each file in the respective slots individually so they flash that way.. You may even need to use a PIT too so it reflashes the partitions..
http://forum.xda-developers.com/ver...mware-firmware-kernel-modem-recovery-t3214560
Click to expand...
Click to collapse
Earlier I downloaded the first "full firmware" at the page that you link. Are you saying I should download each individual file from the second or third down from the top of the page and follow the same instructions that I used this morning that are listed on your instructions to Downgrade back to Lollipop 5.1.1 on Verizon?
Sorry, this is all new to me.
MarkinCCAZ said:
Earlier I downloaded the first "full firmware" at the page that you link. Are you saying I should download each individual file from the second or third down from the top of the page and follow the same instructions that I used this morning that are listed on your instructions to Downgrade back to Lollipop 5.1.1 on Verizon?
Sorry, this is all new to me.
Click to expand...
Click to collapse
No those files are already in the firmware that you downloaded all you need to do is extract them now so it's not a zip file or md5 type so you may have to extract it twice.
MrMike2182 said:
No those files are already in the firmware that you downloaded all you need to do is extract them now so it's not a zip file or md5 type so you may have to extract it twice.
Click to expand...
Click to collapse
Even after extracting the firmware remains a MD5 file?? What type of file should it be?
And again, thank you for walking me through this. Trying to save this phone so I don't have to send it back and wait 10 days to get a replacement.
MarkinCCAZ said:
Even after extracting the firmware remains a MD5 file?? What type of file should it be?
And again, thank you for walking me through this. Trying to save this phone so I don't have to send it back and wait 10 days to get a replacement.
Click to expand...
Click to collapse
What type of extractor did you use? I have 7zip and when you extract the firmware the first time it should go from an md5 to a .zip and then you extract it again and then you should be able to see each of the files..
If I were you I'd immediately take that phone back to the store and get a replacement because there is no firmware number listed like N920VVRS2BPF2 anywhere on the Internet so there's something not right with that.
MrMike2182 said:
What type of extractor did you use? I have 7zip and when you extract the firmware the first time it should go from an md5 to a .zip and then you extract it again and then you should be able to see each of the files..
Click to expand...
Click to collapse
I'll try it with 7zip.
so with 7zip this is what I'm left with:
Where do they go into the lines of Odin - BL, AP, CP, CSC and do they look like the correct files to upload to phone?
MarkinCCAZ said:
so with 7zip this is what I'm left with:
Where do they go into the lines of Odin - BL, AP, CP, CSC and do they look like the correct files to upload to phone?
Click to expand...
Click to collapse
That does look right. Just flash them 1 by 1 in the pda/AP section but go over to options and uncheck reboot so it doesn't reboot on you.. Flash them all system, cache, sboot, recovery, modem, cm.bin and the boot. But not the md5 ones.
MrMike2182 said:
That does look right. Just flash them 1 by 1 in the pda/AP section but go over to options and uncheck reboot so it doesn't reboot on you.. Flash them all system, cache, sboot, recovery, modem, cm.bin and the boot. But not the md5 ones.
Click to expand...
Click to collapse
You are the man. Thank you so much. I'll get started and see where it takes me. :good:
MarkinCCAZ said:
You are the man. Thank you so much. I'll get started and see where it takes me. :good:
Click to expand...
Click to collapse
Make sure you factory reset after you flash them.
---------- Post added at 09:46 PM ---------- Previous post was at 08:59 PM ----------
MarkinCCAZ said:
yes I can get into recovery
Click to expand...
Click to collapse
I found out where the firmware came from N920VVRS2BPF2... That's Verizons newest OTA... Did you accept that today? But the one they have listed still doesn't match yours fully look here..
http://www.verizonwireless.com/support/samsung-galaxy-note5-update/
I think it's to late because that update was a security patch and I think it is the update that finally stops us from being able to downgrad like I posted in my guide.. Even factory reset breaks the phone.. The only way to fix that now is to wait until the firmware is made available to download or send it in for another one.
So I'm SOL?
MarkinCCAZ said:
So I'm SOL?
Click to expand...
Click to collapse
If the firmware you flashed didn't work the last thing you can try is the PIT to repartition the phones partitions and if that doesn't work then yes SOL but you can just take the phone to Verizon and say the update that was just sent screwed up your phone and you'll get another one. You might have to wait a few days but it's better than nothing!
MarkinCCAZ said:
So I'm SOL?
Click to expand...
Click to collapse
Did anything work out with your phone?