Related
hallo guy
(first, my english is bad because i am from germany)
i have installed safestrap and the rom slot 1. i installed/flashed at the rom slot 1 thor gapps rom. after starting the system it came in a bootloop. so safestraped asked me to stop and format it. i thought it means only the rom slot 1. after that on safestrap is the stock rom empty and the other slots too. when i try to make a new rom slot it say there is no space. at the stock rom is only 1230mb space at the system partition. but there is no os. when i try to conect it on my laptop. the laptop dont recognize the kindle. so what can i do ?
kasem71 said:
hallo guy
(first, my english is bad because i am from germany)
i have installed safestrap and the rom slot 1. i installed/flashed at the rom slot 1 thor gapps rom. after starting the system it came in a bootloop. so safestraped asked me to stop and format it. i thought it means only the rom slot 1. after that on safestrap is the stock rom empty and the other slots too. when i try to make a new rom slot it say there is no space. at the stock rom is only 1230mb space at the system partition. but there is no os. when i try to conect it on my laptop. the laptop dont recognize the kindle. so what can i do ?
Click to expand...
Click to collapse
If I remember correctly you have to do these steps after installing the safe trap.
1. create back up from stock rom
2. Create romslot 1
3. restore the back up on romslot 1
4. install the thor gapps rom on rom slot 1.
thor gapps need the stock rom first. that why you create back up and restore it somewhere else. thor gapps is NOT a AOSP room, it removes and modifies the stock rom.
I don't think you can format your stock rom but if you did, you have to wait for a AOSP rom.
Arashkage said:
If I remember correctly you have to do these steps after installing the safe trap.
1. create back up from stock rom
2. Create romslot 1
3. restore the back up on romslot 1
4. install the thor gapps rom on rom slot 1.
thor gapps need the stock rom first. that why you create back up and restore it somewhere else. thor gapps is NOT a AOSP room, it removes and modifies the stock rom.
I don't think you can format your stock rom but if you did, you have to wait for a AOSP rom.
Click to expand...
Click to collapse
the problem is that i cant put anything on my kindle. the laptop dont recognize the tablet. so if a rom come out i cant put it on my kindle. the stock rom is there but its empty !
if
kasem71 said:
the problem is that i cant put anything on my kindle. the laptop dont recognize the tablet. so if a rom come out i cant put it on my kindle. the stock rom is there but its empty !
Click to expand...
Click to collapse
If you could if you can get somebody to send you a backup of some type you can ADB push it to your Sd card in backup directory and restore it . What is your base firmware originally? If you can score a flashable copy of your base that would work also. Four instance the base Hasscode has over in the safestrap thread. (Old firmware) But to get ADB you need to uninstall the Microsoft USB drivers for your device and install the ADB drivers from the utility .94
jimyv said:
If you could if you can get somebody to send you a backup of some type you can ADB push it to your Sd card in backup directory and restore it . What is your base firmware originally? If you can score a flashable copy of your base that would work also. Four instance the base Hasscode has over in the safestrap thread. (Old firmware) But to get ADB you need to uninstall the Microsoft USB drivers for your device and install the ADB drivers from the utility .94
Click to expand...
Click to collapse
thanks for you help. the firmware was the newest. 13.3.2.4. and can you give a step by step tutorial for the ADB ? i wont make it wrong, again
sorry
kasem71 said:
thanks for you help. the firmware was the newest. 13.3.2.4. and can you give a step by step tutorial for the ADB ? i wont make it wrong, again
Click to expand...
Click to collapse
You dont already have the toolkit from development?it has adb drivers try that first .does your device show at all? Maybe with like an explanation point on it and the yellow triangle? If it does open that device in your device manager in and uninstall the drivers. Then run the driver install part of the utility toolkit .94. I'm sorry but no I cannot give you step-by-step or I will not considering it is in these forums at least a dozon times but I'll give you a link to a thread that explains it over and over again but you must be able to comprehend what you are reading and follow directions explicitly it does work it has worked for people but sometimes it takes several attempts . http://forum.xda-developers.com/showthread.php?t=2588608 remember but not just the first post has good information this is discussed all the way through these threads . And often pertain to different subjects . And if you don't think that you find what you need in this thread there are several several other threads in the general section and the troubleshooting section titled brick! Or please help! Or yada yada yada etc. and most will have to do with trying to get ADB back on a device.. For whatever reason. What ever you do do not go to factory recovery attempt a factory reset it will totally screw you. As long as you still have safestrap booting you have hope now you need to do what you did not do to begin with,and educate yourself thoroughly before moving forward with anything . All it will take is one more mistake on your part of the inability to completely read everything and understand everything and you will be calling Amazon for a replacement.. good luck why can't you restore a backup?
hallo
my english is bad, so its diffcult to understand everything. because this i ask for a step by step tutorial. this was my fault.
and is there a difference between the 13.3.2.4.X.X.X versions ? can i take any 13.3.2.4 back up ?
kasem71 said:
hallo
my english is bad, so its diffcult to understand everything. because this i ask for a step by step tutorial. this was my fault.
and is there a difference between the 13.3.2.4.X.X.X versions ? can i take any 13.3.2.4 back up ?
Click to expand...
Click to collapse
Yes. As long as long is it is of a stock system of the same firmware you are on. I am aware of how to do it how to give you a clean backup that would allow you to set it up but I am not on that firmware on any of my three HDX devices And then another idea you may go over to the safestrap thread and inquire about a ABD sideload procedure I did see that option and safestrap recovery but I do not know how it works. Oh and another idea I also know works because I advised it to another person and he did it it worked well for him in a similar situation. Download the original bin file for your firmware to your PC rename the .bin to .zip and download the newest flashable superSU ADB push to SD card then flash to stock slot. Firmware then supersu reboot, reinstall safestrap and redo OTA blocker. It also sounds like you really need to read through the safestrap thread and understand it more thoroughly I do not believe this would've happened if you had more of an understanding on how safestrap is to be used.
jimyv said:
Yes. As long as long is it is of a stock system of the same firmware you are on. I am aware of how to do it how to give you a clean backup that would allow you to set it up but I am not on that firmware on any of my three HDX devices And then another idea you may go over to the safestrap thread and inquire about a ABD sideload procedure I did see that option and safestrap recovery but I do not know how it works. Oh and another idea I also know works because I advised it to another person and he did it it worked well for him in a similar situation. Download the original bin file for your firmware to your PC rename the .bin to .zip and download the newest flashable superSU ADB push to SD card then flash to stock slot. Firmware then supersu reboot, reinstall safestrap and redo OTA blocker. It also sounds like you really need to read through the safestrap thread and understand it more thoroughly I do not believe this would've happened if you had more of an understanding on how safestrap is to be used.
Click to expand...
Click to collapse
when i do this, can i install updates from amazon ?
i cant post anything on the development topic. when i do this, is the device like after a factory reset ?
No!
kasem71 said:
i cant post anything on the development topic. when i do this, is the device like after a factory reset ?
Click to expand...
Click to collapse
Didn't you read in a previous post a couple of post up do not factory reset at least until after you get a working OS and yes you can flash and Amazon bin file BUT safestrap does not flash kernel or bootloader so it will only flash the system partition and data partition and that is what you need. But you have to rename it from .bin to .zip and somehow get it on your device AND YES IT will overwrite any system modifications and root access that's why you must flash the super SU after you flash the firmware zip if you want root right away..that is
jimyv said:
Didn't you read in a previous post a couple of post up do not factory reset at least until after you get a working OS and yes you can flash and Amazon bin file that safestrap does not flash kernel or bootloader so it will only flash the system partition and data partition and that is what you need. But you have to rename it from .bin to .zip and somehow get it on your device
Click to expand...
Click to collapse
ok thanks
If you are still having trouble, go to the developer thread, and rather than posting, try reading and getting the HDX TOOLKIT .94 to work on your computer. That should get adb set up for you. Once that happens, the commands are easy.
$adb push [file location] /sdcard
It doesn't matter
lekofraggle said:
If you are still having trouble, go to the developer thread, and rather than posting, try reading and getting the HDX TOOLKIT .94 to work on your computer. That should get adb set up for you. Once that happens, the commands are easy.
$adb push [file location] /sdcard
Click to expand...
Click to collapse
He didn't listen he chose to do in ADB sideload through safestrap and completely screwed it up now. As far as I know he still has not recovered this device
Hello,
It seems that many of HAM2 users have the consumer cellular variant and are irked by several modifications done on the stock ROM that one gets when he buys the phone unlocked. Many of us, including myself, would like to flash the stock ROM if possible but maybe are not brave enough to try .
Someone uploaded several versions of different ROMS on https://drive.google.com/folderview?...0&usp=sharing. So, the question is can we flash any of these ROMS on our consumer cellular variant and if so, how ? I used to have a samsung galaxy young and flash different countries ROM using ODIN so many times that I can't remember how much. I tried that because it was confirmed to work. So, can the same be done on our HAM2 ?
Thanks.
The problem with flashing oem firmware
medwatt said:
Hello,
It seems that many of HAM2 users have the consumer cellular variant and are irked by several modifications done on the stock ROM that one gets when he buys the phone unlocked. Many of us, including myself, would like to flash the stock ROM if possible but maybe are not brave enough to try .
Someone uploaded several versions of different ROMS on https://drive.google.com/folderview?...0&usp=sharing. So, the question is can we flash any of these ROMS on our consumer cellular variant and if so, how ? I used to have a samsung galaxy young and flash different countries ROM using ODIN so many times that I can't remember how much. I tried that because it was confirmed to work. So, can the same be done on our HAM2 ?
Thanks.
Click to expand...
Click to collapse
The 126 firmware in that folder is the original firmware that came on the consumer cellular version. The problem with flashing the complete 148 firmware is inside udate.app file there is a file named oem_verlist.img. The is a partition in the root directory of the phone for that img file to be flashed. when you go to update with the 148 firmware that img file realizes that it does not match the phone that you are trying to flash to and bring up a error and fails. I have tried to fastboot that img file to its partition but it will not go. Maybe I am using the wrong parition name but with out updating that partition before trying to flash it will fail.
mtyler7807 said:
The 126 firmware in that folder is the original firmware that came on the consumer cellular version. The problem with flashing the complete 148 firmware is inside udate.app file there is a file named oem_verlist.img. The is a partition in the root directory of the phone for that img file to be flashed. when you go to update with the 148 firmware that img file realizes that it does not match the phone that you are trying to flash to and bring up a error and fails. I have tried to fastboot that img file to its partition but it will not go. Maybe I am using the wrong parition name but with out updating that partition before trying to flash it will fail.
Click to expand...
Click to collapse
When you say "update", do you mean clearing the OS and installing a new one from scratch ? Does that mean after the update all the consumer cellular additions will go away and there will be no trace of it ?
If updating seems difficult now for the consumer cellular versions, what will we do when they release Lollipop ?
If they do not release a cc version then I would have to extract the OEM update.app file from the huawei site to all the IMG files and fastboot flash one at a time(force flash if you want to call it). Inside the update file there will be a system.IMG, data.IMG, cache.IMG,etc
Sent from my MT2L03 using XDA Premium 4 mobile app
mtyler7807 said:
If they do not release a cc version then I would have to extract the OEM update.app file from the huawei site to all the IMG files and fastboot flash one at a time(force flash if you want to call it). Inside the update file there will be a system.IMG, data.IMG, cache.IMG,etc
Sent from my MT2L03 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Assuming they release the CC version of lollipop, will there be any problem if some of the system files have been changed? For example, I've deleted some system apps that I never use and changed the boot- and flash-screen files. Will the update fail because of that ? I'm asking this because I saw a video made by one of the forum members here when he was trying to install the v148 update. He had to uninstall everything and return the system to default before updating. If that is so, then I guess no Lollipop crying::crying for me !!
Given that Lollipop is still some months away and the lack of any meaningful activity on the HAM2, why don't we prepare our HAM2 for who-knows-what. I'd like to get a grip on a my phone now instead of getting swamped by error messages when Lollipop gets released or we get custom firmware.
There's this thread [http://forum.xda-developers.com/showthread.php?t=2315547] which explains how to extract the individual image files from the huawei update app.
Do you have the CC version of HAM2 ? If so, will you be trying to flash the image files because extracting the image files seem straight-forward ? I'm actually a bit nervous doing it myself because I've always flashed my other devices when it has been confirmed to work. What I'm wary of is I'm not sure that the device software in the v148 update app is 100% compatible with the CC variant that I own ! How can one be sure of that ?
I've downloaded v148 update file and extracted the files you mentioned. Instead of taking screenshots of the contents of the image files, I've recorded a small video. I can see the boot.img and system.img but no recovery.img. There are also other files. Take a look at the video. The question now is what to do with these files and more importantly what are my chances of unbricking the phone if it bricks !!
It will not fail because of boot animation and splash screen change. It will fail because of missing system apps. You would need to reinstall those if the package comes as a upgrade but if it is a full download then your OK.
Dealing with extracting the files from the update.app just search for my post, I have a complete instruction guide.
Sent from my MT2L03 using XDA Premium 4 mobile app
mtyler7807 said:
It will not fail because of boot animation and splash screen change. It will fail because of missing system apps. You would need to reinstall those if the package comes as a upgrade but if it is a full download then your OK.
Dealing with extracting the files from the update.app just search for my post, I have a complete instruction guide.
Sent from my MT2L03 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Have you seen the video I uploaded ? Is it the "full download"? Can I flash it ? Will the phone brick ?
I read your posts on the subject. But it seems you have changed some system apps and the camera is not working as it should. I have already downloaded the 148 file and extracted the system.img and boot.img files. Can I flash these or do I have to use the files you uploaded on google drive ?
The question is why didn't you use the v148 stock ? I already have the v148 stock. Will it brick my phone if I flash the image files ? If not, why did you have to add extra files there such that the camera is 8MP instead of 13MP. Also, why is the hotspot always enabled ? Is that the case with people with the original stock ?
Man, I'm still waiting for your reply !
medwatt said:
Man, I'm still waiting for your reply !
Click to expand...
Click to collapse
My understanding is it is possible to flash to stock if your bootloader is unlocked and have TWRP installed. Then its as simple as flashing a backup from a matching model with stock frimware. For whatever reason mtyler7807 is trying to reinvent the wheel.
290 said:
My understanding is it is possible to flash to stock if your bootloader is unlocked and have TWRP installed. Then its as simple as flashing a backup from a matching model with stock frimware. For whatever reason mtyler7807 is trying to reinvent the wheel.
Click to expand...
Click to collapse
"For whatever reason mtyler7807 is trying to reinvent the wheel", Ha Ha. I spent about 2 weeks working on this phone when I first got it. With this phone it has more partitions than what is included in the backup with TWRP. TWRP is made for backup and restoring the files that get changed, the other partitions don't change. So when I first started experimenting with this phone I got a full 148 backup with no data and installed it. I had problems, the custom.bin points to a different cust/us/ folder (because it is for a different carrier) , I had to rename that folder and found I have no more 4glte only H/H+, So I had to get the original cust folder from the guy and copy it to the phone. Still and only H/H+. It was okay for then because I testing. Next Viewed my system specs and saw that pretty much half half phone was 148 and the other half was 132.
I have Redone my complete back since I posted the last one with google camera with 13mp support( rather have border transparency). I made a post asking people summit backups. You have to do a little research, did my research and got help from the forum guys. If you want 148 on your CC version you will have to extract the update and fastboot img files (ex.fastboot flash system system.img). The name of the file is the partition name.
From my understanding twrp does a nand backup. Which is more like an image of nand. So restoring an image from a stock phone would also give you the stock partition table no?
It has been a while since ive played with android on such a low level. When it came time to update my HP Touchpad to JB i had to manually create the partition table manually to make it fit. Eventually a script was created that automatically made the changes to the file system. Perhaps a solution along those lines could be useful in getting the stuck firmware on the CC phones? The file system would only need to be created on initial flash to the stock firmware.
mtyler7807, I've been trying to get an answer since I first created this thread. The only reason I want to install the original huawei stock instead of the cc version is because I want to be able to download and install updates just like regular stock huawei HAM2 users instead of waiting for the CC version. So, please can you answer these questions :
1. If I follow your steps and use the image files you uploaded, will I get rid of CC completely meaning will my phone be just like a stock HAM2 phone from Huawei ?
2. Can I install Huawei updates directly, instead of having to do what you did (extracting the image files and the rest of the process).
3. If the answers to the above questions is no and no, then whats the point of installing your images files (apart from getting the hotspot which I don't use) ?
Please answer these questions unambiguously so that I and others will get a clear understanding of the reasons to flash the image files you uploaded. In doing so, people will stop creating these threads asking boundless questions.
Thanks.
medwatt said:
mtyler7807, I've been trying to get an answer since I first created this thread. The only reason I want to install the original huawei stock instead of the cc version is because I want to be able to download and install updates just like regular stock huawei HAM2 users instead of waiting for the CC version. So, please can you answer these questions :
1. If I follow your steps and use the image files you uploaded, will I get rid of CC completely meaning will my phone be just like a stock HAM2 phone from Huawei ?
2. Can I install Huawei updates directly, instead of having to do what you did (extracting the image files and the rest of the process).
3. If the answers to the above questions is no and no, then whats the point of installing your images files (apart from getting the hotspot which I don't use) ?
Please answer these questions unambiguously so that I and others will get a clear understanding of the reasons to flash the image files you uploaded. In doing so, people will stop creating these threads asking boundless questions.
Thanks.
Click to expand...
Click to collapse
Here is what k2thejx5 said after flashing a backup from a stock phone.
k2thejx5 said:
What's weird is when I flashed the stock file and tried to upgrade, it wouldn't work. The kernels were different so I had to go back to stock consumer rom. Also, while using the rom you posted.. I lost my toggles and had to use a different app. What also was very weird, after flashing back to the stock consumer rom, I had tethering! Don't get it lol.
Click to expand...
Click to collapse
-Do what I did makes your phone a complete oem, All that is need to be done is to flash a splash screen.
-How would I know if updates will work since 148 is the latest version for oem, can't test that tell lollipop.
-I'm not pushing anyone to install my image, I got about 30 pm's to post my recovery to enable hotspot and to get those toggles backup at the top. Alot of people messed up and lost them flashing that original twrp recovery under developer. Alot of others wanted the hotspot without the head ache of going through the research.
And for the people with problems with there phone that want 148 and updates with no problems, You should have brought a OEM and stayed away from sears or target or took it back to the store if you were not ready to take on the challenge of fabbing up your phone. Or just deal with the factory image and hope for lollipop.
---------- Post added at 02:14 PM ---------- Previous post was at 02:06 PM ----------
Me and k2thejx5 was trying to fix the problem with the twrp recovery originally posted on this site. That one is not mine. Read the post. That firmware took our toogles away. You have to read this forum a little more.
Ok man, thanks for the reply. Two last question:
-For as long as you've been using your phone with your image files, have you been noticing problems like "unexpected crashes", trying to launch something and its unresponsive lie APN
-Is this the latest file you recommend : [https://drive.google.com/file/d/0BwnSk8BOQp3wV0JMWnJGc3RBTzQ/view]
Thanks.
I have to make another one. I created a new one with epic browser and 360 deg rotation. And I added Camera JB+. Thats the best camera add out there to me, looks just like google 5 camera. I can post image of this new one. I'll Back up my phone and clear the cache and restore it with no data so none of my info will be saved that belongs to me. then i'll setup up the phone and back it up and post.
mtyler7807 said:
I have to make another one. I created a new one with epic browser and 360 deg rotation. And I added Camera JB+. Thats the best camera add out there to me, looks just like google 5 camera. I can post image of this new one. I'll Back up my phone and clear the cache and restore it with no data so none of my info will be saved that belongs to me. then i'll setup up the phone and back it up and post.
Click to expand...
Click to collapse
All right then. Upload it when you're ready !
Well I have just rooted my device by installing ES File Explorer from the Apps Store and then using Silk browser to download towelroot from towelroot.com. Install it using ES File Explorer and run. Click make it rain and the tablet is rooted. Open ES File Explorer again, top left open the menu, select tools and turn Root Explorer ON.
Now I just need to find what to do next and see what roms are available!
Help!?!
well
reconminicon said:
Well I have just rooted my device by installing ES File Explorer from the Apps Store and then using Silk browser to download towelroot from towelroot.com. Install it using ES File Explorer and run. Click make it rain and the tablet is rooted. Open ES File Explorer again, top left open the menu, select tools and turn Root Explorer ON.
Now I just need to find what to do next and see what roms are available!
Help!?!
Click to expand...
Click to collapse
you could have accomplished most of that by one of the utilities in the development section and use same. 95 utility to disable updates. From that point on start reading there are all kinds of new things that are coming out and lots and lots and lots of information.
from what I read, after you have been rolled back BY Amazon you no longer need to OTA updates ?
jimyv said:
you could have accomplished most of that by one of the utilities in the development section and use same. 94 utility to disable updates. From that point on start reading there are all kinds of new things that are coming out and lots and lots and lots of information.
Click to expand...
Click to collapse
It does work with that firmware. Installed Safestrap and the thor 202 rom with gapps and all works fine.
reconminicon said:
It does work with that firmware. Installed Safestrap and the thor 202 rom with gapps and all works fine.
Click to expand...
Click to collapse
Edit: Just received a reply in another thread, it isn't currently possible to rollback 13.3.2.7. Hopefully it's not too far away though. =( If you did find a way too do it with 13.3.2.7 be sure to tell us how you did it then.
reconminicon said:
It does work with that firmware. Installed Safestrap and the thor 202 rom with gapps and all works fine.
Click to expand...
Click to collapse
just trying to clarify here what worked on your firmware?
The utility for the HDX?
did the rep also tell you you would not be eligible for further OTA updates?so no need to use that utility to block them?
Not a further rollback correct?
which safestrap version? operating on which firmware?
after your roll back down to .7. From what firmware?
as far as I have read there is currently not a way to roll back any further than .7 from .5.1 \.5.2 ...=BRICK
so please explain what you are saying here so you are not confusing people into attempting the wrong things
jimyv said:
just trying to clarify here what worked on your firmware?
The utility for the HDX?
did the rep also tell you you would not be eligible for further OTA updates?so no need to use that utility to block them?
Not a further rollback correct?
which safestrap version? operating on which firmware?
after your roll back down to .7. From what firmware?
as far as I have read there is currently not a way to roll back any further than .7 from .5.1 \.5.2 ...=BRICK
so please explain what you are saying here so you are not confusing people into attempting the wrong things
Click to expand...
Click to collapse
I bought it for my mother for Christmas and thought would be better with Andriod.
Got it out the box connected to the internet and it automatically updated to 4.5.1. I contacted Amazon using the SOS app and told them what I wanted to do and they rolled it back. They told me I would not get any future updates and customer service might be hard in the future as it would be running different software version. They requested TS to do it and said it would take two days. The update automatically came through and updated/backdated.
The SafeStrap version would of been the most recent as I think I downloaded it from their site.
The 2.0.2 Thor Rom I mentioned worked fine. The other one would not install. Cannot remember the message I was given but when going onto the Play Store Iand trying to download the daily newspaper it was saying designed for mobile. So I guess it was based on a mobile Rom. This was no good for me and thought my mother was getting along with the Amazon OS quite good. (As she is 67 and its her first device) so I ended up installing the Amazon OS from SafeStrap.
I ended up taking it back to Argos for an exchange, said it was switching itself of as I didnt know how to get rid of SafeStrap on boot and wanted the updates back. My mother loves it.
Amazon also removed the adverts free of charge but after the emplacement they are back. Need to SOS them again.
Hope this helps as I am no pro.
Sorry. Ignore it. Was 13.3.2.6 not 13.3.2.7
kindle fire hdx 14.3.2.8 (apollo 8.9)
greetins,
I received rollback update to 14.3.2.8, is possible to install any other rom instead on this? Tablet is rooted via towelroot, what is next step, what is necessary to do (is possible to install safestrap? may I after this rollback to previous version where is bootloader unlocked?
Thank you very much for your answer.
dont try to rollback you will brick your device
undulus said:
greetins,
I received rollback update to 14.3.2.8, is possible to install any other rom instead on this? Tablet is rooted via towelroot, what is next step, what is necessary to do (is possible to install safestrap? may I after this rollback to previous version where is bootloader unlocked?
Thank you very much for your answer.
Click to expand...
Click to collapse
Well right now you cant do much:
1. Download safestrap and try to install it (should work)
2. If you can enter safestrap make a backup for stock so you can restore if something goes wrong
3. Make a new slot
4. Switch to new slot
5. Install previously downloaded Nexus 2.0.2 rom to created slot (not stock!!!)
6. Reboot and enjoy your kindle
7. Tell us if you succeeded, its possible that safestrap or later nexus wont work because of 3.2.8 kernel
Dont try to roll back you most probably brick your device
jeryll said:
Well right now you cant do much:
1. Download safestrap and try to install it (should work)
2. If you can enter safestrap make a backup for stock so you can restore if something goes wrong
3. Make a new slot
4. Switch to new slot
5. Install previously downloaded Nexus 2.0.2 rom to created slot (not stock!!!)
6. Reboot and enjoy your kindle
7. Tell us if you succeeded, its possible that safestrap or later nexus wont work because of 3.2.8 kernel
Dont try to roll back you most probably brick your device
Click to expand...
Click to collapse
Thank you very much, installation of safestrap and after this rom Nexus 2.0.2 was without problem, all is working, thank you again. But is any way howto rollback to previous firmware - I am not sure version, but as I read, is possible to rollback into version where the bootloader was open and is not necessary to use safestrap ( Safestrap is good, but I have to modifed my partition )
How big partition for system is necessary? Default value was mayby 2.5GB.
And thank you again
Well
undulus said:
But is any way howto rollback to previous firmware - I am not sure version, but as I read, is possible to rollback into version where the bootloader was open and is not necessary to use safestrap ( Safestrap is good, but I have to modifed my partition )
How big partition for system is necessary? Default value was mayby 2.5GB.
And thank you again
Click to expand...
Click to collapse
I am glad you have working Nexus...
For downgrading using known method you must be on firmware xx.3.2.6, xx.3.2.5, xx.3.2.4. Several peoples reported that they bricked their device trying downgrade from xx.3.2.7! You can check here, but you have been warned, dont try that on your device!!! If you brick your device I cant help you, dont know how...
Default size for system partition is fine, I think...
undulus said:
Thank you very much, installation of safestrap and after this rom Nexus 2.0.2 was without problem, all is working, thank you again. But is any way howto rollback to previous firmware - I am not sure version, but as I read, is possible to rollback into version where the bootloader was open and is not necessary to use safestrap ( Safestrap is good, but I have to modifed my partition )
How big partition for system is necessary? Default value was mayby 2.5GB.
And thank you again
Click to expand...
Click to collapse
Hi,
which version of Safetrap you installed? All links I see are for Apollo (in the thread linked above), and my device is Thor. I assume i sould install Safestrap-Thor-3.75-os3.2.4-B02.apk (not Apollos) ?
Also, once installed, is there a way to revert back everything (fire recovery and etc)?
johim said:
Hi,
which version of Safetrap you installed? All links I see are for Apollo, and my device is Thor. I assume i sould install Safestrap-Thor-3.75-os3.2.4-B02.apk (not Apollos) ?
Also, once installed, is there a way to revert back everything (fire recovery and etc)?
Click to expand...
Click to collapse
Safestrap actually doesn't replace the original recovery like TWRP.
All you need to do is uninstall it through that same app, but remember to remove any additional ROM slots or else they'll still be taking up space.
EncryptedCurse said:
Safestrap actually doesn't replace the original recovery like TWRP.
All you need to do is uninstall it through that same app, but remember to remove any additional ROM slots or else they'll still be taking up space.
Click to expand...
Click to collapse
I understand. Its all working now. Its more slow than usual thou.
Another question, once installed Nexus 2.0.2, do I need to root it? Any recommended method? I'm guessing I only need to flash supersu from safetrap, tried searchin in the safetrap topic, but its huge.
For reference: We have two Motorola Moto E (XT1021) devices in our family. Both have been unlocked, rooted, and have TWRP installed. They are running Android 4.4.3.
We would like to upgrade to later versions of Android. However, I am getting conflicting answers on a few issues:
(1) If we just return to the stock bootloader and allow the Motorola update process to continue, will it brick our devices? (Some say yes, some say no... any solid answers?)
(2) In order to upgrade to Lollipop, most of the walkthroughs I have seen say to restore to stock firmware. Is this actually necessary?
(3) If it IS necessary to restore to stock firmware, does anyone have a working link to a current XT1021 stock ROM? Unfortunately, I seem to have lost my copy, and every single link that I have found so far is to http://sbf.droid-developers.org/phone.php?device=34 , which is a dead link.
Thanks in advance for your assistance!
1. Most likely. There have been many users reporting hard bricked devices when the did what you are telling. So you shouldn't risk it.
2. No, it is not necessary if you haven't changed the system a bit, and in such a case just unrooting would suffice. But as you were rooted and all, you may have altered it a little. So it is recommended to flash stock as it removes all chances of errors.
3. Working link:http://forum.xda-developers.com/showthread.php?p=54872420
Hope I helped!!!
Harsh862 said:
Hope I helped!!!
Click to expand...
Click to collapse
Thanks for the answers. I'll definitely have to go back to stock then if we want to upgrade. I hate losing all my settings and high scores, but if that's what has to be done, that's what we have to do.
However, the link for the firmware is for Brasil. So it won't work for me. I'm in the United States, and need the US retail global version for the XT1021. Maybe someone else has this? Thanks in advance!
Also, not sure if it makes a difference or not, but we are still on 4.4.3.
LeiraHoward said:
For reference: We have two Motorola Moto E (XT1021) devices in our family. Both have been unlocked, rooted, and have TWRP installed. They are running Android 4.4.3.
We would like to upgrade to later versions of Android. However, I am getting conflicting answers on a few issues:
(1) If we just return to the stock bootloader and allow the Motorola update process to continue, will it brick our devices? (Some say yes, some say no... any solid answers?)
(2) In order to upgrade to Lollipop, most of the walkthroughs I have seen say to restore to stock firmware. Is this actually necessary?
(3) If it IS necessary to restore to stock firmware, does anyone have a working link to a current XT1021 stock ROM? Unfortunately, I seem to have lost my copy, and every single link that I have found so far is to http://sbf.droid-developers.org/phone.php?device=34 , which is a dead link.
Thanks in advance for your assistance!
Click to expand...
Click to collapse
Que 1&2 are basically the same.
Here is a detailed explanation for both.
To update your OS via official OTA, you need unmodified system. The OTA doesn't simply copy files to the system, it patches those files so if a single file is modified the update won't be able to patch it and your phone will soft brick.
Now, to avoid that, it is recommended to flash stock ROM before updating. Its safe but its a lot cause you just need unmodified system. OTA doesn't care about anything else.(stock recovery is needed too.)
So you can just flash the system partitions and stock recovery. This will not remove your data & those high scores.
To flash just extract your rom and execute these commands ONLY.
Code:
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
You will have your stock recovery and unmodified system ready for update.
neo.ank said:
it is recommended to flash stock ROM before updating. Its safe but its a lot cause you just need unmodified system. OTA doesn't care about anything else.(stock recovery is needed too.).
Click to expand...
Click to collapse
Thanks. I guess I'm stuck because I do not have stock recovery files (I could have sworn I had them backed up but I can't find them anywhere) and I am unable to find them online at the moment (all credible links seem to point back to the dead droid-developers link).
If anyone has a copy of the stock files, I'd love to get them.
LeiraHoward said:
Thanks. I guess I'm stuck because I do not have stock recovery files (I could have sworn I had them backed up but I can't find them anywhere) and I am unable to find them online at the moment (all credible links seem to point back to the dead droid-developers link).
If anyone has a copy of the stock files, I'd love to get them.
Click to expand...
Click to collapse
Stock recovery files are available on xda. Why are going to stock for lollipop upgrade. Use a lollipop flashable file which is given on this page. Don't screw up your device. Link-http://forum.xda-developers.com/moto-e/development/rom-motorola-stock-rom-t2935429
I've done some research and it looks as though the file I need is Blur_Version.21.12.34.condor_retuglb.retuglb.en.US which should be Android 4.4.3 for the XT1021 for the GSM phone in the US. But I am unable to find this rom anywhere. The only file I've been able to get is the 4.4.4 and I don't think that flashing just parts of that one to my device is a good idea. I'd still kinda like to keep my original settings... does anyone have the Blur_Version.21.12.34.condor_retuglb.retuglb.en.US file or a link to it? I have done SO many searches on this site but keep running into dead links. (Whatever happened to droid-developers anyway? ALL the links go to them and nothing works....)
Thanks!
I'm in search of firmware for the S4 running 4.3 or 4.4. I haven't gotten this phone yet but verizon is selling it through Walmart on prepaid. I know the firmware isn't gonna be the same as if it was on contract verizon. I have the S3 right now and it's prepaid. Many argued that there wasn't a NF5 firmware but turns out there is and i used it many times to fix soft bricks on the S3 using Odin. So I'm pretty sure the prepaid side of the S4 will have different firmware then one on contract verizon would have. So that being said, does anyone have 4.3,4.4 or even 5.0 firmware they can share that will work with Odin? Not sure if the S4 got the 5.0 update. Just assuming it did. Any help is appreciated!
Anyone? Please?
If no one can then someone at least tell me how it direct me to where I can make a tar or md5 firmware out of adb pulls of the system an stuff?
bjf189 said:
If no one can then someone at least tell me how it direct me to where I can make a tar or md5 firmware out of adb pulls of the system an stuff?
Click to expand...
Click to collapse
OK never mind. I need 5.0.1 firmware. Not 4.3 or 4.4. Any help would be great
I can't think of any reason as to why post paid firmware would be different than prepaid. You can use the phone for either.
And you're posting jn the wrong forum, which is probably why nobody is helping you. Because you didn't bother to read the rules before posting.
Try the general section or Android development section. Click the search button and type firmware. I'm sure you'll find it faster than it took you to make all these posts. Good luck
still no help
sob372 said:
I can't think of any reason as to why post paid firmware would be different than prepaid. You can use the phone for either.
And you're posting jn the wrong forum, which is probably why nobody is helping you. Because you didn't bother to read the rules before posting.
Try the general section or Android development section. Click the search button and type firmware. I'm sure you'll find it faster than it took you to make all these posts. Good luck
Click to expand...
Click to collapse
still no help
I think what sob372 was saying is the hardware in the phone is the same as the contract so you can just follow the SCH-I545 stuff and it will work.
being that I just got this same phone S4 prepaid used I'll be playing with it to root it, install safestrap and probably downgrade it from Lollipop to Kitkat. So I'll let you know if you don't find more here by searching and I'm sure there are relevant posts if you dig around a bit.
BTW the S4 PP does have a SIM slot.
droidzer1 said:
BTW the S4 PP does have a SIM slot.
Click to expand...
Click to collapse
It just seems really sketchy to do with the contract firmware. Like I get the feeling that if I flash the firmware from contract, I'll lose any cell phone service under prepaid. I just don't want to end up with a big paper weight. The modules could be different. With the S3 I had which was prepaid also. I used safestrap and superlite rom was the best one I got to work with the prepaid version. The system always kept crashing but it would load if I put it under stock an not a rom slot. I had to get the i535pp module to fix the Wi-Fi problem but if I had no service cause of the sim issue then I didn't want it. Also I'm not sure but I think there is no safe strap for the s4 running lollipop. I believe the forum said it would cause bootloops if you tried. Just like you need to deodex for xposed cause of the changes in art
droidzer1 said:
BTW the S4 PP does have a SIM slot.
Click to expand...
Click to collapse
If you can confirm all is in working order with the contract firmware (can't remember what the build is) with the prepaid phone, I'll give it a go.
Update
A member already tried the OC1 postpaid firmware on the prepaid. They said all works but the camera and charging don't work. So that's out of the question
I been looking around on the net and best I've come up with is backing up the firmware. I tried using flash fire to get back ups of every partition. Then I used Odin package creator to try an make a firmware file to use with Odin but when I tried it out in Odin, it stopped at data so I took out my personal data then it stopped at something with number 3 at the end. Can't recall what it was. So if anyone can test more on this to have any luck. Maybe then we can get the firmware out to people in case sammobile decides not to or takes another year to release it
I've been trying a different approach to getting a copy of the OH7 firmware. I've been attempting to use Fiddler4 + the Verizon Wireless Software Upgrade Assistant tool that comes on my phone (Verizon Prepaid Galaxy S4 model SCHI-545KPP) to get a download link to the original rom file... I can't get the bloody link to download with Fiddler or an internet browser, as i get a 403 forbidden error. I'll keep trying, maybe I can find the downloaded file in my temp files while attempting to recover my phone? It will take some time but I'll keep trying.
*update* So I located where the Verizon Wireless Software Upgrade Assistant stores its files (compressed and extracted). The location is C:\Users\[username]\AppData\Roaming\Verizon_AR .
I unfortionally didn't figure this out until after I royally soft bricked my phone. Right now I have a OF1 recovery installed on the phone, and the assistant keeps trying to install the OF1 firmware (and it fails). If anyone could check that folder for the OH7 firmware, or post a backup of the OH7 recovery, you'd be doing me a huge favor. I think we'll have the OH7 firmware after this one way or another.
*edit* This is 100% confirmed now. C:\Users\[username]\AppData\Roaming\Verizon_AR\SCH-I545_I545VRUGOF1_FACTORY\decrypt produced a zip file that is 100% identical to the OF1 firmware zips out there. This decrypt subfolder didn't appear until after the file was completely downloaded, and the Software Repair Assistant had started to try and flash the rom. This data is deleted after the phone completes flashing (or fails to flash). If you select "delete" after this information is downloaded, the encypted rom file is deleted and you must start all over again.
If someone could check that folder who has used the Verizon Wireless Software Upgrade Assistant to recover their phone, using the tool on your phone again and you'll get the decrypt folder... if you zip/rar that folder, we'll finally have the backup files we can post somewhere.
the PP phone uses the same firmware as the normal one that guy that tried it
did something wrong
just flash the OF1 tar via odin and be done with it
TheXev said:
*update* So I located where the Verizon Wireless Software Upgrade Assistant stores its files (compressed and extracted). The location is C:\Users\[username]\AppData\Roaming\Verizon_AR .
I unfortionally didn't figure this out until after I royally soft bricked my phone. Right now I have a OF1 recovery installed on the phone, and the assistant keeps trying to install the OF1 firmware (and it fails). If anyone could check that folder for the OH7 firmware, or post a backup of the OH7 recovery, you'd be doing me a huge favor. I think we'll have the OH7 firmware after this one way or another.
*edit* This is 100% confirmed now. C:\Users\[username]\AppData\Roaming\Verizon_AR\SCH-I545_I545VRUGOF1_FACTORY\decrypt produced a zip file that is 100% identical to the OF1 firmware zips out there. This decrypt subfolder didn't appear until after the file was completely downloaded, and the Software Repair Assistant had started to try and flash the rom. This data is deleted after the phone completes flashing (or fails to flash). If you select "delete" after this information is downloaded, the encypted rom file is deleted and you must start all over again.
If someone could check that folder who has used the Verizon Wireless Software Upgrade Assistant to recover their phone, using the tool on your phone again and you'll get the decrypt folder... if you zip/rar that folder, we'll finally have the backup files we can post somewhere.
Click to expand...
Click to collapse
I'm trying out your idea. If i can get the file them I'll upload it. If not, I'll still be able to at least send you a back up of the oh7 recovery. Mines all still stock. Id hate to get stuck with a paperweight until the correct firmware is released. That's why I'm careful lol. The firmware is downloading right now. It says it's a enc4 file though. Maybe just cause its downloading at the moment. I'll just wait an see an I'll let you know
Legitsu said:
the PP phone uses the same firmware as the normal one that guy that tried it
did something wrong
just flash the OF1 tar via odin and be done with it
Click to expand...
Click to collapse
A few people who used of1 on the pp version had issues. Not one came out with no issues far as i know. So I'd rather be safe then sorry. Not saying your incorrect but I'm just trying to play it safe and careful. Appreciate the input though
bjf189 said:
I'm trying out your idea. If i can get the file them I'll upload it. If not, I'll still be able to at least send you a back up of the oh7 recovery. Mines all still stock. Id hate to get stuck with a paperweight until the correct firmware is released. That's why I'm careful lol. The firmware is downloading right now. It says it's a enc4 file though. Maybe just cause its downloading at the moment. I'll just wait an see an I'll let you know
Click to expand...
Click to collapse
Yes, while it is downloading it will be a .enc4 file. Even after downloading it will stay like that, but when you got to actually flash the file, it will decrypt and the encrypted version will appear in that /decrypt folder.
TheXev said:
Yes, while it is downloading it will be a .enc4 file. Even after downloading it will stay like that, but when you got to actually flash the file, it will decrypt and the encrypted version will appear in that /decrypt folder.
Click to expand...
Click to collapse
so im confused. do i need the encrypted or decrypted file for it to work with odin? i tried changing the file to zip format and open it with winrar after it downloaded in the software but it came up as an unknown archive or damaged. so im not sure what im doing wrong but ill keep trying
UPDATE: i have tried getting the file through verizons handy tool and i did get the decrypted folder along with the unzip folder during it was finishing up repairing my s4. i just copied the file from the decrypted folder and extracted it during the repair. so now im using odin 3.10.7 and testing it out now to see if it will flash successfully. if all goes well, i will make new thread with the firmware link inside it so users dont need to scroll through pages to find the link. first anyone know a good or popular upload storage i can use to upload the firmware to for others to use? i tried uploading onto here but i keep getting a connection timeout
UPDATE 2: ive got it! i made the firmware of OH7! finally. you can go ahead and head over to this thread TheXev. use it and youll be back to stock
http://forum.xda-developers.com/gal...nt/firmware-release-galaxy-s4-i545pp-t3365371
bjf189 said:
so im confused. do i need the encrypted or decrypted file for it to work with odin? i tried changing the file to zip format and open it with winrar after it downloaded in the software but it came up as an unknown archive or damaged. so im not sure what im doing wrong but ill keep trying
UPDATE: i have tried getting the file through verizons handy tool and i did get the decrypted folder along with the unzip folder during it was finishing up repairing my s4. i just copied the file from the decrypted folder and extracted it during the repair. so now im using odin 3.10.7 and testing it out now to see if it will flash successfully. if all goes well, i will make new thread with the firmware link inside it so users dont need to scroll through pages to find the link. first anyone know a good or popular upload storage i can use to upload the firmware to for others to use? i tried uploading onto here but i keep getting a connection timeout
UPDATE 2: ive got it! i made the firmware of OH7! finally. you can go ahead and head over to this thread TheXev. use it and youll be back to stock
http://forum.xda-developers.com/gal...nt/firmware-release-galaxy-s4-i545pp-t3365371
Click to expand...
Click to collapse
Thank you so much. I was close to taking this phone back and not getting another simply because I really need a phone to replace my S3 for tethering soon. But if you got the firmware, I can flash it back to working order, and hopefully get some deodexed roms (that way I can install Xposed framework). Thanks again!