How do get into recovery thingy? I have searched for the answer and have seen no mention of the exact step by step method. I think I have CWm installed but I'm not sure as I can't get to it. I also can't see my TF from win 7. This I have also searched for and there is no mention of it anywhere. I have plugged my TF into every audio port on my computer and it just won't recognize it. Which is the better Rom? I would like to know in case I ever get in the recovery thingy to flash a rom. How do I change kernals? Which is the better kernel? Do any of them support 2 Ghz overclocking? I have spent the last week reading the whole forum and have found none of the answers to these questions. Can someone make a video on entering the recovery thingy?
Edit: I just searched and I couldn't find this post so I almost had to make another post to get people to help me find this one. Luckily I found it by mistake
i need some help rooting my strat i been following this guide http://rootzwiki.com/topic/7840-kernel-guide-root-your-stratosphere/
and i already flashed the kernel already and im on the part where u need to put your phone into usb debugging and so i plug my phone in and let it install its drivers and then i open up CMD in windows and i copy and paste this command F:\Downloads\heimdall-suite-1.3.1-win32>adb devices
to see if it detects my device and it just says device not ready... soo that is where i am stuck at i have downloaded and installed android sdk and did the updates with it and i close out of it and then do the same thing in cmd and still says device not ready..... im lost
i placed android sdk under the root of my C drive called android im running windows 7 64bit
redid the WHOLE walkthrough went and reinstalled adk, and re doing the kernel file to the phone and now im back at the same part but now i get this, there is no disk in the drive please insert a disk into the drive /device/harddisk2/DR2.
and all i get is cancel try again and continue and when i do it again its the same thing..... it seems this is just a simple thing but being stupid
ill donate 15$ to who ever helps me and completes this with me lol
good job? lol didnt do anything
Did u get it I'm in the middle of rooting mmine. Still seting up adb on new laptop.
yea im still stuck BUT someone on a different forum gave me this http://rootzwiki.com/topic/9711-untested-odin-for-stratosphere/ but im a little scared to test this because this is the only phone i have
rooting thur odin right now.... wish me luck
well that didnt work and bricked
does anyone have the stock files to odin back to stock?
.
Thread moved. Would advise you to read forum rules and post in correct section.
Failure to comply with forum rules will result in an infraction and/or ban depending on severity of rule break.
I can't seem to find a Clockwork Recovery install anywhere and was wondering what the progress was in the port? I seen that someone posted they were working on it on the root thread and need to know if any updates on it? I know there are a ton of people that won't go without a slider and seeing as this phone is the only 4g slider right now I figured there would be all kinds of rom support for it. Its unlocked bootloader was the reason i got it along with my fiancee's need for a keyboard. First time i seen any android device without cwr.
cydetrakd said:
I can't seem to find a Clockwork Recovery install anywhere and was wondering what the progress was in the port? I seen that someone posted they were working on it on the root thread and need to know if any updates on it? I know there are a ton of people that won't go without a slider and seeing as this phone is the only 4g slider right now I figured there would be all kinds of rom support for it. Its unlocked bootloader was the reason i got it along with my fiancee's need for a keyboard. First time i seen any android device without cwr.
Click to expand...
Click to collapse
Ill donate to a dev who doesnt have the phone buts wants to dev
Sent from my SCH-I405 using Tapatalk
samsung stratosphere trouble!!
Hi everyone. I was looking for some help to fix the samsung stratosphere that i tried rooting the other day. I will explain to the best of my knowledge as to what i did and how i got where i am with trying to root my phone and where i believe things went bad. i downloaded heimdall and all the necessary files that i got off of the rootzwiki forum specifically for rooting this phone. I was following the instructions exactly as they are posted. Well i than tried to use a different method within heimdall called heimdall - front end. i tried flashing the kernel from the rootzwiki forum using this method. i loaded the stratosphere.pit and went to the flash menu and checked repartition and reboot phone and clicked flash. Thats where the trouble began,now it seems that my phone is stuck in a bootloop,where it will either go to the screen where it asks if you wanna flash a custom rom or it will go into recovery mode if i try to reboot the phone. When my phone is plugged in, it dont show thats its charging but the power button will work sometimes or i just have to hold the power and volume down button and it will go to the custom rom screen. If anyone could help me figure this out,it would be greatly appreciated and thanks in advance for any help or advice on my situation.
Ok so I am unsure if someone is filtering out OLD topics but i keep coming across FORUM posts from people and it seems like they are getting no help or being referred to NON existent topics.
I just recently bought a HTC ONE M8 H/K from sprint. I have had android for a decade and am seriously tired of the ROOT it people. so I figured why not no down falls and everyone says it is easy. Well I am Murphy last name law and you people have not seen or know the things I am about to post
I recently spent over 32 hours watching video and preparing for ROOTING. I unlocked phone got Pilz touch recovery and everything worked fine. I even got CWM and SUPERSU and Busy box. all of which needed OTHER files to work properly. Again a few forced quits everything was fine.
I wanted to Switch to TWRP and the install didnt go through. however now I have BOOTloop. trust me this is the tip of the berg at this point.
Just short of finding NO help after another 24hrs binge session on the CPU and just shy of RUNNING MY PHONE OVER WITH A DAMN CAR>
I get oh so simple easy fix and the only posts I see are FIXED IT!!! so that helps me approximately as much as my phone helps me make phone calls currently.
After the boot loop SEVERAL friends versed in this so called ROOTING (which I still find to be a hoax and not actually possible by any means at this point and time.) and no one has any clue. Tried flashing ROMS RUU's everything comes back to NO will not work.
Then it brings me to the STOCK RUU config for the HK M8 which seemed like it was going to work through ADB flash but guess what. 2 hrs idle NOTHING. after that The recovery program dropped out and boot loader only stated RUU in the menu. (something never before logged in a forum or post as I can tell) after many attempts to do GOD KNOWS WHAT WITHOUT ANSWERS as i was about to smash my beautiful gold phone into a dozen tiny peices and claim accident the Recovery came back to...... You guessed it NOTHING. All directories are UNMOUNTED and cannot be mounted.
I am stuck. Seriously you all fix my phone or help i am willing to send gifts because I am out 700$ now on this nice paperweight but everything and everyone tells me. OH SO SIMPLE you have recovery it aint no thang.
Well guess what it is and I am tired of being so PISSED OFF for something that was so automated.
Again I am Murphy and what you attempt to get me to follow will come up with some REALLY weird repercussions I will post back.
Please oh mighty gods of ruining my life. Spare me this one thing I will never ask for another again.
How do I get my phone to just WORK, Simple. Right?
Hi there! I think I found a thread that can get you back on track. Please read every word carefully and follow every step. If you have further trouble or want to clarify anything, please ask in the thread. They know the device best and can help you I'm sure.
http://forum.xda-developers.com/showthread.php?t=2503646
I'm afraid that is the extent of what we do in the XDA Assist Section. We are guides...pointing people in the right direction when they can't find what they are looking for. Unfortunately we don't do hands on support in this section, so as I said....if you need a further hand, I am sure someone in the thread I linked can help.
And make sure anything you download and flash is for your model. And as always, do a Nandroid backup in recovery... before flashing anything new....it can be a lifesaver to help restore you when you hit trouble.
Good luck!
Details
Let me re iterate.
All guides are demanding S-Off (cannot as I cannot acess phone apps to do so)
All guides need HOME access for apps to modify certain things
I cannot:
Push packet through adb as they are unreadable
Get past boot screen
Recovery is only 40% operational with visibilty of phone only working sometime.
Cannot flash
Cannot push
Cannot fastboot
Cannot see device on CPU as it is stuck in recovery
ALL DIRECTORIES in /SDCARD have been removed
No Firmware
No RUU
No img
As far as I can tell.....Phone is empty and cannot be populated with anythin. I did manage to get SuperSu pushed through and installed. But how do I open it?
No ROOT access as well in the recovery.
I followed ALL STEPS of EASY guides even downloaded one button app that runs it all for me. Can't talk to phone does not see it in ADB.
The other guide I went to was helpful but I have already attempted all of those things.
With an empty phone NO DATA and no ability to get ADB to even run data over cable I am baffled.
I did exactly like the 500 guides i read said.
1) bootlock unlock
2)instal recovery (Philzmod)
3) get CWM (retrieved from playstore) Need a .zip to run in ADB
Phone worked fine until I changed from Philz mod to TWRP which never took place. Philz mod still runs but TWRP said it installed.
Now I have a completely worthless empty phone and I have cried about a tub worth of tears over the 700 i will be dropping over the next year for a piece of metal.
Oh and 99.9% of time if ADB DOES do something either no directory once pushed, cannot read or cannot FIND/Open directory stating BAD installation aborted I NEED a better recovery
I understand your frustration. Not a fun situation at all.
As I said, XDA Assist is here to help navigate the website. Not to troubleshoot I'm afraid.
The purpose of XDA Assist... http://forum.xda-developers.com/showthread.php?t=2764768
The very best place to ask for help in your situation is right here, in the Q&A section for your device... http://forum.xda-developers.com/showthread.php?t=2764768
The people there know your device best. Start a thread that's to the point, polite and accurate....what is exactly wrong, and the exact steps you took to get there. And hopefully help will follow.
Hope it can be solved for you!
Hi all, a few months ago i had a perfectly running rooted TF101 with stock asus firmware. It has CWM recovery v6.0.1.3 and i had the CWM app installed.
somewhere along the timeline i decided it was a good idea to backup the whole thing using the CWM app just in case anything funny happens. Now don't ask me how or why it went the way it did, but the CWM app seemingly performed its backup, there was a disclaimer warning somewhere about possibly losing root access, to which i think i said "yes", the device rebooted and my entire image was gone - only left with CWM recovery mode.
I have been trying to reflash it with stock recovery image, but the SD card won't mount. I am also unsure whether i still have root access or not.
in terms of connectivity, all i was able to get back was ADB access, which i was able to search xda and find threads such as these to try and fake an sdcard then reflash
https://forum.xda-developers.com/showthread.php?t=911228
I've tried katkiss image and stock image but everytime i get a status 7 error or an error 21
https://forum.xda-developers.com/nexus-6p/help/zip-file-signature-verification-error-t3561054
https://www.**********.com/fix-status-7-error-while-installing-ota-update-or-roms/
I'm not exactly an ADB crackhead and I'm not able to get past it so i've searched some more and found on xda again threads on using EasyFlasher, I've followed the instructions but can't get the APX drivers installed on windows 10.
https://forum.xda-developers.com/showthread.php?t=1688012
basically, at this stage i've read many articles, many posts, none have worked because links are outdated or instructions are outdated and mostly i'd rather stop trying all i am finding without really understanding before i brick this device for good out of ignorance.
sure it's old but it was functioning properly and was being used actively by my kids. if i can get it back to life, that'd be nice.
has someone experienced (and fixed) something similar or feel can contribute to unbricking my device?
Thanks guys.
I'm a noob myself, but I managed to get the APX driver installed on Win 10 (just now) by following the directions at how to geek dot com. I used "Option two: Use an Advanced Boot Option."
Good luck!
I've got the Oukitel WP16 which a 64 bit and has an octa-core MediaTek Helio P60 MT6771V on Android 11. Actually a pretty decent rugged phone. Originally tried to root it through fastboot and bricked it about 2 weeks after getting it. For the life of me, I couldn't bring it back to life. Finally after 4 months of it just sitting in a drawer, I went about flashing it to bring it back to life a little differently than I was before and it stuck. Very thankful that it was working again because in those months I had destroyed 3 of your average break if you touch them phones. However me being me, getting it going again wasn't enough. So I gave rooting it a try again. Got it! Rooted with Magisk. Now because I have one of those devices I believe is under rated and under developed, I can't find any kind of development done on it whatsoever and want to build/port TWRP so I'm able to try a GSI ROM. My problem is that every tutorial I read or watch has nothing like what is my stock ROM. Either names of files are different or I find the files in other folders, I've got more folders than what I'm trying to port, and, I would need to double check again, but I wanna say that I've even found them in different partitions. So my question is, what do I do? Like fstab is not in the recovery but in something else. That something else that has fstab in it, my port doesn't have that folder at all. And there are others like that. I've tried several, I repeat SEVERAL different tutorials and cannot figure out what to do. I know it's beyond the capabilities of the tool, but I even tried one of those Hovatek port tools. Obviously didn't work because of the kernel. So to say I'm lost is an understatement. This isn't the first phone I've tried this with. Had another 64 bit with the same chipset that actually had a unofficial TWRP built for it. But when it came to try to port a ROM, I was left with files in different folders and things that weren't in the ROM i was trying to port. I eventually just have up because I kind of had to since scuba diving with the phone here in the Mexican Caribbean finally took it's toll on the phones external hardware. But yeah, back to my only question. What do I do in this situation? I'm mainly concerned about it because this WP16 has a night vision camera on it which I use quite often and don't want to lose that. Recovery has nothing to do with the camera but the ROM I'd like to port will. So figuring out what to do with the recovery could eventually lead me to my answer with the ROM. Anyway, kind of a long winded explanation just to get to what may seem like a simple question to some. Any help would be greatly appreciated.
finnroth69 said:
I've got the Oukitel WP16 which a 64 bit and has an octa-core MediaTek Helio P60 MT6771V on Android 11. Actually a pretty decent rugged phone. Originally tried to root it through fastboot and bricked it about 2 weeks after getting it. For the life of me, I couldn't bring it back to life. Finally after 4 months of it just sitting in a drawer, I went about flashing it to bring it back to life a little differently than I was before and it stuck. Very thankful that it was working again because in those months I had destroyed 3 of your average break if you touch them phones. However me being me, getting it going again wasn't enough. So I gave rooting it a try again. Got it! Rooted with Magisk. Now because I have one of those devices I believe is under rated and under developed, I can't find any kind of development done on it whatsoever and want to build/port TWRP so I'm able to try a GSI ROM. My problem is that every tutorial I read or watch has nothing like what is my stock ROM. Either names of files are different or I find the files in other folders, I've got more folders than what I'm trying to port, and, I would need to double check again, but I wanna say that I've even found them in different partitions. So my question is, what do I do? Like fstab is not in the recovery but in something else. That something else that has fstab in it, my port doesn't have that folder at all. And there are others like that. I've tried several, I repeat SEVERAL different tutorials and cannot figure out what to do. I know it's beyond the capabilities of the tool, but I even tried one of those Hovatek port tools. Obviously didn't work because of the kernel. So to say I'm lost is an understatement. This isn't the first phone I've tried this with. Had another 64 bit with the same chipset that actually had a unofficial TWRP built for it. But when it came to try to port a ROM, I was left with files in different folders and things that weren't in the ROM i was trying to port. I eventually just have up because I kind of had to since scuba diving with the phone here in the Mexican Caribbean finally took it's toll on the phones external hardware. But yeah, back to my only question. What do I do in this situation? I'm mainly concerned about it because this WP16 has a night vision camera on it which I use quite often and don't want to lose that. Recovery has nothing to do with the camera but the ROM I'd like to port will. So figuring out what to do with the recovery could eventually lead me to my answer with the ROM. Anyway, kind of a long winded explanation just to get to what may seem like a simple question to some. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Your device already have TWRP [Firmware version: OUKITEL_WP16_RU_V04_20220621 ] but you not need Custom Recovery for install GSI. Use stock recovery.
About GSI with a night vision camera support so is much expensive solving that. You can try but need very experience and patience of the tests and solutions.
lopestom said:
Seriously? Thank you! I'm guessing the link is gonna be in 4pda being that it's Russian? I've spent a month searching and haven't found anything whatsoever. And since I don't read Russian, I always overlook 4pda even though it's been a great resource in the past. And yes, I'm aware you don't "need" custom recovery for GSI's. It does make things a little easier for me though.
Click to expand...
Click to collapse
The recovery issue will be solved since there is a recovery out there. That still doesn't solve the mystery and problem i have of files being in different places though. In that case what do I do if the files isn't in the same place in the port as it is in the stock, or the other way around? Add the stock file to the same folder it is in for the port? Or should I make a new folder in the port that's name is the same as in the stock? If neither, what do I do?
finnroth69 said:
Seriously? Thank you! I'm guessing the link is gonna be in 4pda being that it's Russian? I've spent a month searching and haven't found anything whatsoever. And since I don't read Russian, I always overlook 4pda even though it's been a great resource in the past. And yes, I'm aware you don't "need" custom recovery for GSI's. It does make things a little easier for me though.
Click to expand...
Click to collapse
No! Search my repository in the github in the release option.
finnroth69 said:
The recovery issue will be solved since there is a recovery out there. That still doesn't solve the mystery and problem i have of files being in different places though. In that case what do I do if the files isn't in the same place in the port as it is in the stock, or the other way around? Add the stock file to the same folder it is in for the port? Or should I make a new folder in the port that's name is the same as in the stock? If neither, what do I do?
Click to expand...
Click to collapse
As I wrote before, it is very difficult to solve issues like the original stock ROM camera. There are even one or two people who managed to get this to work.
Now what you don't understand: If you want a Custom ROM, use GSI and adapt, solve, analyze and test by changing some stock ROM files in GSI. You must understand that you need experience and time. You can even compile a Custom ROM - any GSI - specifically for your device. So you just need to have the source code of your device, have the GSI source code and know how to compile the file so that you can do the tests. Again, you must understand that you need experience and time.
If you haven't researched what is GSI and still think that Custom ROMs portability that happened before until Android 7.1 then look, read and update yourself.
In your questions, be as detailed as possible. You write a lot of parts and you scramble the words.
As for having GSI normally I already wrote where there is an instruction to install and you follow. As for TWRP, look it up on my github.
As for solving something in the GSI, if you managed to install it and still used the phh options to try to fix any bad part, then it is only you who will be able to solve any error/adaptation/bug/extra installations that there.
Trust me when I say I understand what you're saying. I have done some testing I have watched tutorials, I have studied. but everything that I have seen is basically switching a file from a folder on the stock ROM to a folder in the ported ROM with the same name as what's in the stock ROM, and possibly adding a little script to something. What I'm trying to figure out is what I asked. Fstab is not in recovery on my phone's stock ROM. It is in something else. But fstab is in and a part of recovery for TWRP. So even though there might be a TWRP for my phone doesn't help me to know if I should be creating that same folder that's in my stock ROM in the ported one for fstab or other files that are like it. I have downloaded the TWRP from your profile and I've gone to the 4pda and discovered that you're the dev who ported it with and without encryption. Nice work and thank you! I would like to move beyond being a flash baby though. So I'm simply trying asking that one specific question to help me learn because it is something I am lost on. Whether it is to port recovery, port a ROM, or whatever, I don't know what to do when the location of the files I need to port from the stock aren't matching with the with the location of the files in the port itself. Fstab is just one example. I'm gonna send you a friend request. Later when I fire up my laptop, I'll take screenshots to physically show you exactly what I mean. Please be patient and don't get upset at me for trying to learn. As well as please take your time in responding. It's no rush since I've got a business to run and this is something I'm trying to teach myself on the side. It really is something I'm lost on, and if I'm lost on it, how many others has it confused as well?
As for the camera app issue. We can forget I asked that also. I understand completely what you're saying about it being far beyond my reach right now. Thank you for the heads up on that.
Mr. Lopestom can you please help me with your recovery images? I cannot seem to get any of them to boot. I've tried the with script found on 4pda, without that script, I've tried flashing an empty vbmeta, but nothing is getting the images to boot. See attachment for script I'm talking about. Attachment only shows me running it, but I have tried without.
What sense does it make to flash an empty VBMETA ? You typically pull the existing VBMETA and pass this file to Fastboot what rewrites 2 bytes in that file.
finnroth69 said:
Mr. Lopestom can you please help me with your recovery images? I cannot seem to get any of them to boot. I've tried the with script found on 4pda, without that script, I've tried flashing an empty vbmeta, but nothing is getting the images to boot. See attachment for script I'm talking about. Attachment only shows me running it, but I have tried without.
Click to expand...
Click to collapse
The problem is not in the vbmeta file. You can use this one if you can: Post in thread 'Looking for a walkthrough on installing a custom ROM on a BLU G90 PRO' https://forum.xda-developers.com/t/...om-rom-on-a-blu-g90-pro.4253737/post-85180967
The big fact is that the company put a recovery.img stock file inside /vendor/etc/ and you should know how to deal with it. So only removing this recovery.img and repacking modified vendor.img made by u; install that in your device so you can have TWRP.
jwoegerbauer said:
What sense does it make to flash an empty VBMETA ? You typically pull the existing VBMETA and pass this file to Fastboot what rewrites 2 bytes in that file.
Click to expand...
Click to collapse
I'm not sure to be honest with you. Like I told lopestom, I'm just trying to teach myself as I can in my free time. A lot of what I do is imitate what I see or read. While reading post about flashing twrp i had read something about flashing an empty vbmeta file.