heey guys,
i am facing a problem, i have installed the alternative OS called asteroid os and want to go back to android wear 1.5 or 2.0 i honestly don't care about either of them. i've been in the flash scene for a while now so i'm actually sure what i'm doing.
here is the install instruction from asteroidos:
https://asteroidos.org/install/swift/
problem is the following:
i've tried all the instructions to install the stock images of the system, boot and recovery, flashing via fastboot doesn't work, there are no error messages, but i always end up in the boot loop (android male of stock recovery). formatting the system partition ends with an error that only works with the erase command. i strongly suspect that the partition sizes have been changed. now my question to you is there a way to change them back to stock?
even if i boot twrp (which only works if i don't flash the image boot directly) i can't install anything via adb sideload.
i am really at the end of my latin
Related
So I just got into this stuff last week and have learned quite a bit. I tried various types of images. Accidentally I happened to load the Android 1.6 dev image to my regular G1. Now it wont let me flash anything! It wont let me flash images or even the spl! Please help me!!! How do I get back to cupcake now?
You mean the stock ADP1v1.6 image from developer.htc.com?
First off, you do NOT want to be flashing the SPL. The first thing you should have done is to write the ENGINEERING SPL (ADP1 stock SPL), and then NEVER touch the SPL again.
Now since you managed to write the stock ADP1v1.6 image, I suspect that you already have this (or the uselessly different hack of it called HARDSPL), which means that you have a mode called FASTBOOT (which can be used to write ANY image (in image format, not in update format) to the device. I suggest flashing the RECOVERY partition with cyanogen's recovery image. You can use fastboot to do this. The fastboot binary and instructions on getting into fastboot mode is available at developer.htc.com/adp.html -- the command to use would be "fastboot flash recovery recovery.img".
Note: With a stock ADP1v1.1 or newer, root access is available (yes, stock root), but only via ADB -- this is a SECURITY precaution to prevent malicious apps from hijacking root. If you want to su to root, just need to go in via ADB. So in other words, if somehow you have a stock tmobile SPL that lacks fastboot, then you DO have root access, so you can go in and flash the recovery partition over ADB. What you would do here is copy the recovery.img onto the root of your sdcard and use the flash_image command... i.e. "flash_image recovery /sdcard/recovery.img".
Hey
I have got a kinda big problem. I wanted to factory reset my phone, because apps were not responding, force closing and I had a lot of apps installed (I am on B135), so I went in my TWRP 2.8.1.0 recovery and factory resetted. cache was unable to mount, so I only wiped data and rebooted. The same problem now occurs only worse.
I thought about the cache that might be causing this, but all attemts to wipe it (recovery, apps) failed.
I also thought I could flash the stock recovery again and force update the phone, but the 3 button method isnt working and (of course) I need the stock recovery
Someone please help
EdrichVerburg said:
Hey
I have got a kinda big problem. I wanted to factory reset my phone, because apps were not responding, force closing and I had a lot of apps installed (I am on B135), so I went in my TWRP 2.8.1.0 recovery and factory resetted. cache was unable to mount, so I only wiped data and rebooted. The same problem now occurs only worse.
I thought about the cache that might be causing this, but all attemts to wipe it (recovery, apps) failed.
I also thought I could flash the stock recovery again and force update the phone, but the 3 button method isnt working and (of course) I need the stock recovery
Someone please help
Click to expand...
Click to collapse
I would suggest that you install the latest twrp with flashify and then update your phone, because the newest twrp has the emui updater already built in, so you don't have to re-flash recoveries all the time.
Thanks Sproker,
One problem though. The lastest twrp does not seem to work because it is EMUI 3.0 and I am on EMUI 2.3?? I recently fixed it finally, but I still want to upgrade to EMUI 3.0... Is it worth it? And if it is, what am I to do?
Download the update.app (B135)
And extract the recovery.img
Now download ADB/Fastboot and the latest driver (HISiute).
Connect your phone with the computer and boot your phone into recovery mode.
Now boot into bootloader mode and search the device with "fastboot devices" if it is correctly connected, it should be displayed.
Now flash (first move the recovery.img into the ADB /Fastboot folder) the recovery.img you extracted before.
"fastboot flash recovery recovery.img"
Now you should have the stock recovery back on your phone.
But if twrp didn't work (erasing cache) the stock will also not work.
Try to erase cache via fastboot. But I don't know the code...
so firstly, let me make this clear, i had Android 6 stock rom working initially, i installed TWRP and rooted the phone with SU
All was working fine until i decided to try and wip the phone to test either a lineage os build or the new EMUI 5
However after performing factory reset, the /data partition is now broken.
I know i'm not the only one that has encountered this issue, but i would at least like a straight forward answer in order to resolve the problem.
Stock recovery now doesn't seem to be an option as when i send it to the phone, i reboot and TWRP still exists.
i have tried via fastboot and from within TWRP, i still get the /data partition error if trying in TWRP to flash recovery.
surely there is a proper solution for this, as this is a software issue not a hardware issue.
i would appreciate your assistance and can provide whatever required information necessary.
i did not pay $500 for this phone for it to be a useless brick
I noticed something here about modaco-rc3 recovery, which i am downloading to try, if it flashes properly, as i suspect this /data partition issue is preventing much of anything from being modified now.
i look forward to your responses and will reply to this with an update after trying to flash modaco recovery if successful
The data partition of the EMUI roms are different than what for example lineageos needs (I think because of encryption).
You need to flash the stock recovery via fastboot, then wipe and format data from there, then TWRP should be able to mount the partition again. In TWRP you can format the partition again to the format according to what is necessary for the rom you want to install.
christopherpfister said:
You need to flash the stock recovery via fastboot, then wipe and format data from there, then TWRP should be able to mount the partition again. In TWRP you can format the partition again to the format according to what is necessary for the rom you want to install.
Click to expand...
Click to collapse
I am just downloading 4.1 stock rom i found finally on Huawei website after much buggering around last night, clearly it was a long day.
Will get this flashed with the stock recovery that I was able to put back on thanks to SRKTool
Will update again shortly, thank you for the reply.
failed to mount system for rom install
now this is just getting silly...
so i was able to restore stock rom with the dload folder procedure and EMUI recovery restored with SRKTool
successfully then unlocked bootloader, put on twrp-3.0.2-0-eva-modaco-rc3, did the data wipes and tried to install lineage os zip.
(the original problem of going back to stock rom is solved, but this is still ongoing as to now why a custom rom will not load)
now i get the infamous ERROR: 7
after
could not detect filesystem for /dev/block/bootdevice/by-name/system, assuming ext4
mount: failed to mount /dev/block/bootdevice/by-name/system at system: no such file or directory
....this is all seeming far too difficult to install any custom rom on this unit, what is happening?
same issue
I'm having a similar issue, any updates?
I am now planning to switch to Official LOS on my wife's Android G1 a.k.a. SEED,
is there a way to restore everything to its original form like official rom, recovery, boot and even relock bootloader?
I was a previous Nexus 5 user and I can eflash the rom image file from google and relock bootloader in just a few type on CMD but I can't seem to find image rom for official SEED(G1).
You'll find most of the stuff you need here. But it's kinda outdated. No factory image for flashing through fastboot though and the latest zip is marshmallow MRA58Y
Basically you'll want to
1. Flash the MRA58Y zip thru TWRP
2. Flash the OEM.img of your G1
3.. If you changed splash screen you can also flash stock splash screen from fastboot
After that your almost all stocked and ready to go
Just need to get rid of the custom recovery. Which is kinda tricky, the stock rom flashes stock recovery all by itself, the tricky part is triggering it as TWRP tries to disable it from happening. One way to stop TWRP from blocking it is to mount system partition and read only reboot to stock then try to reboot to recovery to check it if it's back to stock . Good luck and here's the link
https://drive.google.com/folderview?id=0B9_eDTtTcnv1a25ERUxGcm9CSzA&usp=sharing#list
You mean when flashing MRA58Y I need to mount System partition then flash to restore stock recovery?
By the way i already downloaded OTA of nougat
I can only seem to get into fastboot mode with a Menu saying:
Restart Bootloader
Unlock Bootloader (Unlocked)
Wipe Userdata
Exit
I haven't been able to get to any download mode at all, just this menu and stock recovery, can someone please give me instructions on this? I've gotten different files and ways to root this from many different threads and I'm confused as hell.
Never rooted this RP2 before, it's on latest OTA MR2-RC001-RZR-190914.3123. Got it unlocked before and it's been unlocked for a while but didn't go further with rooting because I got confused and didn't want to brick my expensive phone. Last phone I rooted was back on kitkat or lollipop before I switched to iPhone, so I'm not a total noob just rusty. But Razer got me back to Android and it''s changed alot. I need detailed advice please. :good: And if my instinct is telling me correctly I'd assume something is changed about the bootloader in MR2 thats affecting me right now?
That menu is the bootloader/download mode.
DarkestSpawn said:
That menu is the bootloader/download mode.
Click to expand...
Click to collapse
My issue was not having Bootloader interface installed. Fixed
MarkusGingles said:
My issue was not having Bootloader interface installed. Fixed
Click to expand...
Click to collapse
Have you unlocked critical partition?
https://developer.razer.com/razer-p...6.1692205032.1582602359-1206928491.1581902985
Razer recommends you use a USB 3 Type-A to Type-C spec-compliant cable for any device flashing.
THE CABLE THAT CAME WITH THE PHONE WILL NOT WORK.
If you have everything unlocked then make sure you do this
https://s3.amazonaws.com/cheryl-fac...stall_Android_Fastboot_Drivers_on_Windows.pdf
Or install using this tool
https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445
If you make it this far then it's a matter of typing in the correct path in fastboot.
fastboot flash boot "arter97 name here".img
Then from the fastboot menu scroll down to boot to recovery or type fastboot reboot recovery
TWRP should boot if you installed the correct kernel.
In TWRP hit cancel then swipe to make modifications and install magisk 20.3
Profit
JDBarlow said:
Have you unlocked critical partition?
https://developer.razer.com/razer-p...6.1692205032.1582602359-1206928491.1581902985
Razer recommends you use a USB 3 Type-A to Type-C spec-compliant cable for any device flashing.
THE CABLE THAT CAME WITH THE PHONE WILL NOT WORK.
If you have everything unlocked then make sure you do this
https://s3.amazonaws.com/cheryl-fac...stall_Android_Fastboot_Drivers_on_Windows.pdf
Or install using this tool
https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445
If you make it this far then it's a matter of typing in the correct path in fastboot.
fastboot flash boot "arter97 name here".img
Then from the fastboot menu scroll down to boot to recovery or type fastboot reboot recovery
TWRP should boot if you installed the correct kernel.
In TWRP hit cancel then swipe to make modifications and install magisk 20.3
Profit
Click to expand...
Click to collapse
Okay so I couldn't flash anything originally simply because i didn't have Bootloader Interface installed. Figured that out and had everything working, unlocked, Arter Kernel 12, Magisk 20.3, EdXposed, and now after I edited build.prop to enable my regular hotspot without carrier permission and reboot. Well now I really can't flash sh?t. Even though I can get into bootloader & Recovery, when I try to fastboot flash MR1 Stock or MR2 stock just to get back into the phone it freezes on the razer logo and eventually reboots and repeats. Then i have to Reflash arter to get back into TWRP after I try to flash anything else which otherwrites Arter97.img. Finally read the red text in TWRP and /data was refusing to mount, fixed that by a basic ass wipe (DUH) Hoping that might have been the issue, my data folder was corrupt or my old data folder was mismatching with the rest of the new roms i tried to flash? Idk someone smarter plz tell me. So far my next attempt is going to be downloading a flashable Stock Deodoxed ZIP to see if flashing from within TWRP now that /Data will mount makes a difference compared to Fastboot. Tried fastboot flashing MR1 and MR2 Normal Razer Stock Rom after data remounted and now i can get to the green vortex/visualizer screen instead of just the Razer Logo before it STILL loops and then when it loops again a second time it sends me to TWRP automatically.
MarkusGingles said:
Okay so I couldn't flash anything originally simply because i didn't have Bootloader Interface installed. Figured that out and had everything working, unlocked, Arter Kernel 12, Magisk 20.3, EdXposed, and now after I edited build.prop to enable my regular hotspot without carrier permission and reboot. Well now I really can't flash sh?t. Even though I can get into bootloader & Recovery, when I try to fastboot flash MR1 Stock or MR2 stock just to get back into the phone it freezes on the razer logo and eventually reboots and repeats. Then i have to Reflash arter to get back into TWRP after I try to flash anything else which otherwrites Arter97.img. Finally read the red text in TWRP and /data was refusing to mount, fixed that by a basic ass wipe (DUH) Hoping that might have been the issue, my data folder was corrupt or my old data folder was mismatching with the rest of the new roms i tried to flash? Idk someone smarter plz tell me. So far my next attempt is going to be downloading a flashable Stock Deodoxed ZIP to see if flashing from within TWRP now that /Data will mount makes a difference compared to Fastboot. Tried fastboot flashing MR1 and MR2 Normal Razer Stock Rom after data remounted and now i can get to the green vortex/visualizer screen instead of just the Razer Logo before it STILL loops and then when it loops again a second time it sends me to TWRP automatically.
Click to expand...
Click to collapse
Have you tried the format data partition ?
MarkusGingles said:
Okay so I couldn't flash anything originally simply because i didn't have Bootloader Interface installed. Figured that out and had everything working, unlocked, Arter Kernel 12, Magisk 20.3, EdXposed, and now after I edited build.prop to enable my regular hotspot without carrier permission and reboot. Well now I really can't flash sh?t. Even though I can get into bootloader & Recovery, when I try to fastboot flash MR1 Stock or MR2 stock just to get back into the phone it freezes on the razer logo and eventually reboots and repeats. Then i have to Reflash arter to get back into TWRP after I try to flash anything else which otherwrites Arter97.img. Finally read the red text in TWRP and /data was refusing to mount, fixed that by a basic ass wipe (DUH) Hoping that might have been the issue, my data folder was corrupt or my old data folder was mismatching with the rest of the new roms i tried to flash? Idk someone smarter plz tell me. So far my next attempt is going to be downloading a flashable Stock Deodoxed ZIP to see if flashing from within TWRP now that /Data will mount makes a difference compared to Fastboot. Tried fastboot flashing MR1 and MR2 Normal Razer Stock Rom after data remounted and now i can get to the green vortex/visualizer screen instead of just the Razer Logo before it STILL loops and then when it loops again a second time it sends me to TWRP automatically.
Click to expand...
Click to collapse
Will it not let you flash stock using flash_all.bat file while in fastboot mode?
I would definitely try and start over for sure if possible