Related
Ok, so I recently bought a used dell streak off of a friend, and although I like it, I don't like dell's ROM, so my main goal here is to install a custom rom.(Specifically, streakdroid 2.0.0). I was able to root my phone, however I am having issues flashing the recovery image,to get to installing the custom rom. I have tried using rom manager to install clockwork, and when I do it says it installs fine, but when I tell it to reboot into clockwork, the phone just boots up normally into android.When I boot using power + vol up + vol down, it just boots into the stock recovery image. I have also tried using fastboot to flash the recovery image using the clockwork recovery image for the dell streak. The command line says the flash was completed, yet again when I boot into the recovery image it is still the dell streak stock recovery image. I also renamed the file: system/ect/install-recovery.sh to system/ect/install-recovery.sh.bak , following another post's advice, still no luck. I have spent several hours looking on forums on how to fix it, and can't find anyone with this problem on the dell streak. I have also tried to find a way to install a custom ROM without using a recovery image, but haven't been able to do that either. Any help at all would be greatly, greatly appreciated, even a possible tip to point me in the right direction.
For some more info about my phone, I do believe that it might be a corporate edition, I don't know if that would effect anything or not, the other details are as follows:
Model Number : Dell Streak
Android version: 2.2.2
Baseband version: GAUSB1A135100-US
Kernel version: 2.6.32.9-perf
OEM Version: GAUSB1A135100
Build number : 15609
Custom Recovery – Prevent Overwriting on Dell Streak
I already tried the advice given on that link. I can't even get into the custom recovery image even one time.
Also I meant to post this under the Q & A forum, if it's possible for someone to move this post, I'd appreciate it.
damoshemeister said:
I already tried the advice given on that link. I can't even get into the custom recovery image even one time.
Click to expand...
Click to collapse
Rename install-recovery.sh before you install the custom recovery. If the phone boots even once the recovery is over written with the stock recovery if you don't.
Also - there are a bunch of posts that state that ROM Manger does not work on the Streak.
I have also tried using adb to flash the recovery image after renaming the file and immediately booting into the recovery image after installing. Still same issue. Also without even renaming that file, I believe I am still supposed to be able to access the custom recovery image one time.
You do have to enter the stock recovery to get into ClockworkMod or StreakMod. It's what you do after you get into stock recovery that takes you into CM or SM.
Rather than tell you how to do it, I will tell you to READ those guides posted above for the answer. If you don't want to do that, then you should stop messing with something you don't understand before you brick your new toy! The Streak doesn't root, recover, or update ROMs like other Android devices.
Ok, while I did have legitimate issues with rom manager it turns out I had a misunderstanding of how to install streamod,as you pointed out. Please forgive me, I was pouring over a ton of information in a very short amount of time, including being completely new to android, how to install apks from a pc, jailbreaking, using adb fastboot to flash images, all for the first time. I didn't realize you had to update from within the stock recovery image to install streakmod. I appreciate your help allot. I was able to successfully install streakdroid like I wanted, wouldn't have been able to do it without your help. Thanks again.
Glad to see you got it up and going. I can understand your frustration. The first time I played with my Streak I bricked it and took it to someone to fix and he didn't know much more than I did about it.
When I got it back unfixed, I spent several days reading and now consider myself fairly proficient in the art of flashing, although I haven't made any steps into cooking up my own ROMS or all the other technical stuff that goes with what these unselfish guys go through for us.
Have fun!!
damoshemeister said:
Ok, while I did have legitimate issues with rom manager it turns out I had a misunderstanding of how to install streamod,as you pointed out. Please forgive me, I was pouring over a ton of information in a very short amount of time, including being completely new to android, how to install apks from a pc, jailbreaking, using adb fastboot to flash images, all for the first time. I didn't realize you had to update from within the stock recovery image to install streakmod. I appreciate your help allot. I was able to successfully install streakdroid like I wanted, wouldn't have been able to do it without your help. Thanks again.
Click to expand...
Click to collapse
Sorry to have been so tough on you. That's the only way to get people to UNDERSTAND what they are doing to their devices. Now that you found it on your own, you will remember it. You also stumbled onto some other info that may not pertain to your situation now, but you will remember seeing it in the future when you need it!
Here is another concise guide that is excellent and a short read:
http://forum.pocketables.net/showthread.php?t=8715
Good Luck!
kraz
Yea, I definitely understand where you guys are coming from. I do like to try to figure stuff out on my own, and did spend some considerable time reading before I posted on this forum. You guys gave the exact help I was looking for, just a nudge in the right direction. Knowledgeable people can save newbs like me hours in frustration.What threw me off was partially bad luck, but definitely due to incomplete understanding as well. It was the combination of rom manager not working , and me not properly understanding how to install streakmod that led to me thinking it had something to do with the bootloader blocking the recovery image from being flashed. I thought I was gonna end up having to flash the bootloader but definitely didn't want to do this as that would have been very vulnerable to bricking. I read the basics on the different images, and what they did before I tried anything. I did end up at one point with my streak not being able to boot, or update from an update.pkg but since I knew I didn't touch the bootloader, I knew I should be able to get it up and running again. THanks for the link, I will definitely read it.
did u try
flash the clockworkmod or the other recovery image. when the flash was done, it will boot the dell streak, meanwhile, press vol up and down, boot into the recovery mood again, I mean NEVER let the streak boot into the rom afte u flash the image.
Sent from my Dell Streak using XDA App
marvin02 said:
Rename install-recovery.sh before you install the custom recovery. If the phone boots even once the recovery is over written with the stock recovery if you don't.
Also - there are a bunch of posts that state that ROM Manger does not work on the Streak.
Click to expand...
Click to collapse
what do i rename " install-recovery.sh " to?
thanks
I renamed mine to "install-recovery.sh.bak", but I have seen "do-not-install-recovery.sh". In other words, you can rename it to whatever you want.
Strephon Alkhalikoi said:
I renamed mine to "install-recovery.sh.bak", but I have seen "do-not-install-recovery.sh". In other words, you can rename it to whatever you want.
Click to expand...
Click to collapse
every time i try to rename it i get a failed message. any other suggestions? thanks for the help in advanced
You have to mount the internal SD as R/W, it's in R/O it sounds like
trucutu62 said:
every time i try to rename it i get a failed message. any other suggestions? thanks for the help in advanced
Click to expand...
Click to collapse
As noted by the post just prior to this one, the system partition is read-only. You need to change it temporarily to read-write using a file manager that can do the job. I used Super Manager, but there are plenty of root file manager apps on the Market that can do the job.
Hello everyone, First off I would like to thank all of those that have posted on this site and contribute to it.
Now to my problem. Let me share a little history of how everything started.
I first rooted my MT4G about a year ago, Tried to use IcedGlacier but it was not loading properly so I used cyanogenmod 6 I believe? I wanted to try IcedGlacier but It still was not loading properly. Then when I tried to restore it would not restore properly. At this point it appeared to be bricked but bootloader still worked but the PD15img file was not found. So after some researched I downloaded it and it restored my phone back to factory condition. Now I want to try other roms again because I'm getting bored of stock and attempting to load different kernels but this is where my issues are beginning.
As you can see in the attached photo that is what the bootloader looks like. I thought it was weird that next to hboot it says "HBOOT-0.85.2007 (PD1510000)".
(I tried to post the image but since I'm a noob I and unable. If you want to see the screen shot of my bootloader just message me.
I was thinking maybe this is a reason as to why now No other rom but the stock one will load. Also what is weird is that when it goes into bootloader it still says PD15img is not found but the phone will start up fine with the stock rom.
The phone remains rooted but No Rom or Kernel will Load and fully install.
When It loads roms it goes to install it shuts off and reboots into stock rom.
I tried to Use the PD15IMG.zip on the SD card to see maybe if it didn't load properly but it will begin to load with the blue bar in the corner but then after it goes all the way up nothing else happens.
I have been trying to look for answers but haven't found any real answers that help me fix my problem.
So if someone can help me I would greatly appreciate it.
The "no PD15IMG.zip" message is supposed to appear. When the bootloader loads, it checks the root of your SD for that file, and if it's not there, you'll get that message. Nothing wrong with that.
Since you're perm-rooted and running the engineering boatloader, you just need to make sure your recovery image is good. If you haven't already, download ROM Manager from the Market and use that to install a fresh copy of ClockworkMod recovery. From there you should be good to flash any ROM you want.
Thanks, I did what you said plus I realized when I was downloading the roms using a Mac and my Mac would unzip the file automatically and trying to compress it back to a zip doesn't work at all. But thanks alot for the help!
If the PD15IMG.zip doesnt work you probably dont have the part7-xxxxxxxxxx.zip file on your sdcard
Sent from my HTC Glacier using XDA Premium App
Alright, I'm new around here. I searched around a lot on the forums, but didn't find a similar problem.
Phone model: Motorola Defy XT (XT535)
Carrier: It's GSM. So, it doesn't matter, does it?
I found many threads talking about the rooting process of Defy XT, and some of them did help me conduct it without problems. I did meddle around for some time after rooting; Eventually I thought I will change the stock ROM (GB - 2.3.7).
The problem is that, I couldn't find a tested (official/unofficial) ClockworkMod recovery for use with Defy XT. I could do with installing some Chinese release of ICS for Defy XT (SBF), but, I wanted to try CM10; it appeared more fascinating. So, anyway, I thought I could use Koushik's custom recovery build script on his website (builder.clockworkmod.com). So, I did the process of obtaining the stock "recovery.img", plugging it in that script, and obtained a new custom-built CWM. The real problem which I am not able to come out of is now - After flashing it, on the next reboot, it is going into the "MBM-flash mode", and it throws out an "error 0301", and doesn't go further than that. In this mode, I gathered that it will be able to communicate to a computer (RSD lite) over USB, and so, I installed it and was able to detect the device, but I'm not able to find out, what to do next to get it back to normal working condition.
Since that error screen I see now is basically a flashing tool, I was thinking, reflashing the recovery partition with the stock "recovery.img" (have a back up) should solve the problem. But, I'm not able to find out how to do it...
If there is anyone else who has faced a similar problem and found a solution, it would be really good of you to share it. Or, if there is anyone who knows how to work with RSD lite, could you suggest a method to flash the "recovery" section only through this software? (I'm guessing an XML file should be enough, but I don't know how to write it; format).
Hopefully I'll get speedy replies .
QuaziRandom said:
Alright, I'm new around here. I searched around a lot on the forums, but didn't find a similar problem.
Phone model: Motorola Defy XT (XT535)
Carrier: It's GSM. So, it doesn't matter, does it?
I found many threads talking about the rooting process of Defy XT, and some of them did help me conduct it without problems. I did meddle around for some time after rooting; Eventually I thought I will change the stock ROM (GB - 2.3.7).
hi i have faced same problem with my defyxt when i was testing cwm like you i got same error
the solution is just flash the sbf files by using rsd lite dats it bt you will lost your data
Click to expand...
Click to collapse
I tried...
Srika said:
QuaziRandom said:
hi i have faced same problem with my defyxt when i was testing cwm like you i got same error
the solution is just flash the sbf files by using rsd lite dats it bt you will lost your data
Click to expand...
Click to collapse
Yes... I was trying since yesterday. I was thinking of making a custom SBF to flash the recovery partition with the original one, but seeing the responses on this thread, I decided to cut to the chase and flash it with the Chinese ICS instead (and lost all my data of course). I succeeded to get my phone back up and running, but now, I have nothing but the bare minimum on it. I am trying to root and it, and get all my required apps back.
I still would prefer getting CWM recovery on this. Will keep trying...
Click to expand...
Click to collapse
QuaziRandom said:
Srika said:
Yes... I was trying since yesterday. I was thinking of making a custom SBF to flash the recovery partition with the original one, but seeing the responses on this thread, I decided to cut to the chase and flash it with the Chinese ICS instead (and lost all my data of course). I succeeded to get my phone back up and running, but now, I have nothing but the bare minimum on it. I am trying to root and it, and get all my required apps back.
I still would prefer getting CWM recovery on this. Will keep trying...
Click to expand...
Click to collapse
Yep i have succeded to extract our stock recovery image and stock kernal
I have tried to make a cwm by koush website script bt it showed me a fail
Click to expand...
Click to collapse
Srika said:
QuaziRandom said:
Yep i have succeded to extract our stock recovery image and stock kernal
I have tried to make a cwm by koush website script bt it showed me a fail
Click to expand...
Click to collapse
any other way to backup my stock rom b4 flashing the new ics rom?
Click to expand...
Click to collapse
Please ask all questions in the Q&A section. Thread moved there.
Unfortunately all the TWRP flashable roms from GetOffMyLawn&!+¢#{$ are dead and I need the stock rom for the MetroPCS variant. Anyone know where I can find it?
I think I mostly got to where I needed to go with the stock factory roms without using TWRP. After attempting and failing to make a flashable rip with Android Kitchen, I read about and saw a video on RSD Lite here youtube.com/watch?v=njXQYn53SPc (sorry can't hyperlink since my post count) It basically just quickly shows what it should look like and how it should work IF it works once setup. But it was good enough. The images I had were giving me failing to flash gpt and bootloader errors. So I manually took those complete lines out of both the flashfile.xml and the Servicefile.xml. After that it flashed everything and rebooted. To my surprise I'm not bricked and back on stock. I had to go back to enable Device Carrier Unlocking through the metropcs app (oops). Now I have to probly unlock the bootloader and root again but this time I'll make that backup
But if anyone has the flashable zips, a new upload would be nice for others.
unrooty said:
I think I mostly got to where I needed to go with the stock factory roms without using TWRP. After attempting and failing to make a flashable rip with Android Kitchen, I read about and saw a video on RSD Lite here youtube.com/watch?v=njXQYn53SPc (sorry can't hyperlink since my post count) It basically just quickly shows what it should look like and how it should work IF it works once setup. But it was good enough. The images I had were giving me failing to flash gpt and bootloader errors. So I manually took those complete lines out of both the flashfile.xml and the Servicefile.xml. After that it flashed everything and rebooted. To my surprise I'm not bricked and back on stock. I had to go back to enable Device Carrier Unlocking through the metropcs app (oops). Now I have to probly unlock the bootloader and root again but this time I'll make that backup
But if anyone has the flashable zips, a new upload would be nice for others.
Click to expand...
Click to collapse
Send me an untouched stock system.img, boot.img, and oem.img and I'll compile you a TWRP flashable ROM. If you're not sure how to dump partition images, the best way is to download an app called Partition Backup & Restore. It's a free app and was created by an XDA dev @wanam.
Hey, thanks for the offer. I'll do it. I have the img files that you need ripped and rared. Just been having some connection issues today while attempting to upload the file. I don't know how I should upload it so I'm going to use my google drive and share the link with you either here or by PM if I can't link it here due to the spam protection. Hopefully I'll have it to you within the next day if my connection becomes stable enough to upload.
https://drive.google.com/open?id=1x65mPUAWWm1heQsDRpgm6QYnyyOIp8P5
Here you are MotoJunkie01, I decided to keep the extended name on the file to show exactly what Partition Backup and Restore spit out should there be something different that's needed.
unrooty said:
https://drive.google.com/open?id=1x65mPUAWWm1heQsDRpgm6QYnyyOIp8P5
Here you are MotoJunkie01, I decided to keep the extended name on the file to show exactly what Partition Backup and Restore spit out should there be something different that's needed.
Click to expand...
Click to collapse
I made one yesterday. Read my guide carefully. Have fun. https://forum.xda-developers.com/mo...-stock-rom-t3777830/post76234878#post76234878
Quite the write up there, thank you for it it's very informative. But to be fair flashing through RSDLite it working for me so I suppose I'll stick with it. It seems more straightforward afaik.
unrooty said:
Quite the write up there, thank you for it it's very informative. But to be fair flashing through RSDLite it working for me so I suppose I'll stick with it. It seems more straightforward afaik.
Click to expand...
Click to collapse
Good choice. I, personally, don't see how that's a better option than just rsdlite. But to each his, or her, own. If you need no verity, magisk, and all the basics anyway, why not just flash the stock firmware. No risk involved.
unrooty said:
Quite the write up there, thank you for it it's very informative. But to be fair flashing through RSDLite it working for me so I suppose I'll stick with it. It seems more straightforward afaik.
Click to expand...
Click to collapse
Yep - seems a better choice. RSD Lite isn't the friendliness beast but it's not a bad ride once you understand the idiosyncrasies.
So I didn't happen to back up my scatter or boot.img files when I used fastboot to try and flash the TWRP for the onn 10 inch, I was assuming it would work, but now I'm stuck with no recovery, no fastboot, no system, won't boot up when you hold the power button.
The only method of recovery I have is through MTK preloader and spflash, but I don't have the correct factory images or scatter file required to reflash stock. I've been looking everywhere online and can't find the right recovery files or any guides on how to recover from this.
Any help/files/advice would be greatly appreciated!!
Two things, I got access to my old account after a password reset
and, I got my tab back up and running, as well as root & xposed + gravitybox
I'm working on a guide as we speak.
Also, I will be dumping my firmware and adding the 10001885 to the list of stock image dumps on the main onn thread.
Hope this helps if still needing it, scatter file for the 100011885 mt8168 , good luck not responsible for anything lol i still cant get mine to work, anklosburner
Ankylo'sburner said:
So I didn't happen to back up my scatter or boot.img files when I used fastboot to try and flash the TWRP for the onn 10 inch, I was assuming it would work, but now I'm stuck with no recovery, no fastboot, no system, won't boot up when you hold the power button.
The only method of recovery I have is through MTK preloader and spflash, but I don't have the correct factory images or scatter file required to reflash stock. I've been looking everywhere online and can't find the right recovery files or any guides on how to recover from this.
Any help/files/advice would be greatly appreciated!!
Click to expand...
Click to collapse
hope this helps if you still need it for 100011885 mt8168 scatter file, but not responsible for any damages, because i still cant get mine to work, i had it to where it would come on, or i could see back light but thats it, which im impatient too, maybe it takes a min, but i did a readback on every downloadable item and flashed it but idk, let me know if you or how you get yours to work if you do
bbcdt22 said:
Hope this helps if still needing it, scatter file for the 100011885 mt8168 , good luck not responsible for anything lol i still cant get mine to work, anklosburner
hope this helps if you still need it for 100011885 mt8168 scatter file, but not responsible for any damages, because i still cant get mine to work, i had it to where it would come on, or i could see back light but thats it, which im impatient too, maybe it takes a min, but i did a readback on every downloadable item and flashed it but idk, let me know if you or how you get yours to work if you do
Click to expand...
Click to collapse
Hey, i've had that same issue but have since fixed it by flashing the rom to the 100011886. I used some of the posts here to flash both vbmeta.img and boot.img to gain root, with success https://drive.google.com/drive/folders/17LtLtjKg4JJU9EJdIXPsyNjen0H-ilMX?usp=sharing . i eventually went too far and currupted my rom and had a hard time finding the stock ROM. I found the stock ROM to the 100011886 and flashed that to fix the problem, now i run that as my system and it boots up just fine. https://www.mediafire.com/file/107jp6gwbiwq87q/MT8168_ONN_Gen2_100011886.zip/file
fastboot erase super
fastboot flash super super.img
Would you happen to have the preloader bin file for the MT8168? After digging around, you have helped me get closer to bringing my hard brick back to life.
Edit: @bbcdt22
onn. said:
Would you happen to have the preloader bin file for the MT8168? After digging around, you have helped me get closer to bringing my hard brick back to life.
Edit: @bbcdt22
Click to expand...
Click to collapse
I don't, but this thread may help:
[STOCK] Stock Backups/Images/OTAs
Since these tablets don't have an external online resource for downloading system updates, only a sketchy OTA app (com.adups.fota) I'm collecting a library of OTAs, as well as boot/recovery/system images. I have access to a 10.1 with keyboard...
forum.xda-developers.com
Any rom you come across has to be extracted in order to get any necessary files from it. The thread mentions using 7zip but I've personally had better results extracting using ZArchiver. Also, a workaround I've found very useful when dealing with extraction issues, is removing the extension from the file. If all else fails, you may need to erase the super partition and reflash THAT
KMerrimanJr said:
I don't, but this thread may help:
[STOCK] Stock Backups/Images/OTAs
Since these tablets don't have an external online resource for downloading system updates, only a sketchy OTA app (com.adups.fota) I'm collecting a library of OTAs, as well as boot/recovery/system images. I have access to a 10.1 with keyboard...
forum.xda-developers.com
Any rom you come across has to be extracted in order to get any necessary files from it. The thread mentions using 7zip but I've personally had better results extracting using ZArchiver. Also, a workaround I've found very useful when dealing with extraction issues, is removing the extension from the file. If all else fails, you may need to erase the super partition and reflash THAT
Click to expand...
Click to collapse
Thanks for the response. I'm at the end of that thread currently trying to see what I can find to fix my issue. Aside from buying another one from Walmart and trying to see if I can pull everything from a vanilla tablet, I'm not sure if I'll ever find the exact files.
onn. said:
Thanks for the response. I'm at the end of that thread currently trying to see what I can find to fix my issue. Aside from buying another one from Walmart and trying to see if I can pull everything from a vanilla tablet, I'm not sure if I'll ever find the exact files.
Click to expand...
Click to collapse
onn. said:
Thanks for the response. I'm at the end of that thread currently trying to see what I can find to fix my issue. Aside from buying another one from Walmart and trying to see if I can pull everything from a vanilla tablet, I'm not sure if I'll ever find the exact files.
Click to expand...
Click to collapse
When my tab crashed on me, flashing the super image solved my issue but it was a different rom. My tab's model number ended in 885 but the super file I flashed came from an 886, it still worked though
KMerrimanJr said:
When my tab crashed on me, flashing the super image solved my issue but it was a different rom. My tab's model number ended in 885 but the super file I flashed came from an 886, it still worked though
Click to expand...
Click to collapse
I wish I would have waited until I read this today instead of further messing with it yesterday. It looks like everything you have is what I need, but now I am battling trying to get the COM port to stay active when the device is plugged in. I'll tinker with it and see if I can get back to the state I had it in yesterday where it was staying connected.
KMerrimanJr said:
When my tab crashed on me, flashing the super image solved my issue but it was a different rom. My tab's model number ended in 885 but the super file I flashed came from an 886, it still worked though
Click to expand...
Click to collapse
Would you happen to know/remember all the settings you checked in SP Flash Tool (I assume you used that) when you flashed things to get it working? It seems that my PC is able to communicate with the device again, but I'm unsure of how to proceed next.
Have you installed all of the adb & mtk drivers? If so, you should be able to use adb to reboot into the boot loader then use fast boot to flash the super file
KMerrimanJr said:
Have you installed all of the adb & mtk drivers? If so, you should be able to use adb to reboot into the boot loader then use fast boot to flash the super file
Click to expand...
Click to collapse
It's hard bricked at the moment unfortunately, so there's no appearance of life to it. Attached picture is the error I get. https://www.gizmoadvices.com/list-sp-flash-tool-error-codes-solution-fix/ appears show info about the error, but it's not something I know how to fix yet.
The only way I can get the tablet to make moves in device manager (which I assume is a sign that the PC can at least partially recognize/see the device) is to click on Download in SPFT, connect tablet to PC via USB cord, and then hold down power button, which led to the error. Errors in SPFT I've received so far are 0xC0060001 and 0xC0060003.
When the tablet is active in the device manager, I assume that the device is in a powered state. However, when the device is grayed out, I assume it's in a powered off state (see other pic). I've yet to find away to actually flash anything to it.
KMerrimanJr said:
Have you installed all of the adb & mtk drivers? If so, you should be able to use adb to reboot into the boot loader then use fast boot to flash the super file
Click to expand...
Click to collapse
Also, apologies if I'm being a bother, but do you know what version of SPFT you used as well as which DA file?
bbcdt22 said:
Hope this helps if still needing it, scatter file for the 100011885 mt8168 , good luck not responsible for anything lol i still cant get mine to work, anklosburner
hope this helps if you still need it for 100011885 mt8168 scatter file, but not responsible for any damages, because i still cant get mine to work, i had it to where it would come on, or i could see back light but thats it, which im impatient too, maybe it takes a min, but i did a readback on every downloadable item and flashed it but idk, let me know if you or how you get yours to work if you do
Click to expand...
Click to collapse
where did you get this? did you dump it? if so how?