Running 2.3.3, build number is CL 49208, using a Mac. Unlocked bootloader with fastboot. Used recovery-RA-passion-v2.2.1. Put the su-2.3.6.1 on my phone. Finally got it to reboot in recovery. Installed CM7.0.3. Oh, and I bought this phone in China (it's legit). Also, I used info from lots of sources before I finally found a recent post here that suggested the su zip file. One of those things I put in my sdcard is Radio_20100203_2_Signed_PASSION.img. Don't know if that helps. I couldn't find a more updated radio image.
The plan is to install CM7 so I can run openvpn.
It stops and cycles through the CM7 load screen -- turquoise android on a skateboard with an arrow circling around. Goes no further.
What did I miss? How do I fix it? Thanks.
Sounds like your in a bootloop.
Did you flash GAPPS also?
Here's more infos for radio, ect...
http://forum.xda-developers.com/showthread.php?t=744605
Has happened to me before. I removed the SD card and scanned it for errors on my PC. Worked after that. HTH.
Sent from my Nexus One using XDA App
Uhh...I can't put a microsd card in my computer -- I don't think.
Would you recommend updating the radio image? I'm thinking the 5.12.00.08, since my phone is in fact Korean. Do I still need the GAPPS image? Can I flash that image into my phone, or do I need to put it on the root of the sdcard?
cat3rpill3r said:
Uhh...I can't put a microsd card in my computer -- I don't think.
Would you recommend updating the radio image? I'm thinking the 5.12.00.08, since my phone is in fact Korean. Do I still need the GAPPS image? Can I flash that image into my phone, or do I need to put it on the root of the sdcard?
Click to expand...
Click to collapse
They make an adapter for micro sd card t ofit a USB port.
You can try new radio but If it's bootlooping I think your problem is elsewhere.
Did you check MD5SUM of the ROM before flashing?
Fortunately, my neighbor has a plethora of microsd adapters.
I did not check the sum. I read a few suggestions about doing that, but I couldn't figure out how, so I just trusted that what I had was fine. Lesson learned.
Let me get this straight: I need to put the GAPPS image on the sdcard AND flash the GAPPS image from fastboot? If I do update the radio image, do I need to reinstall CM7?
Put cm7 rom and gapps on sd card,
boot into recovery and flash rom then gapps, reboot.
Its highly recommends you do radio via fastboot.
To check md5sum, you can use one of the many free app from market.
Ok, ran checksum in fastboot. Not really sure what I'm looking for, so I'll just post what happened. In every case except gapps and su, the numbers returned were the same on the sdcard as in the tools file on my mac. Gapps and su are only on the sdcard.
For the CM7 zip, it returned: MD5(pathtofile)= 98d06d6a58c7de87d40269bfe0ae0e7b
For the RA img: 3def709ab1c9e051a92a1c8b1504a36a
For the Radio img: 310d85c4998163818f7dcdef730c2a12
For the gapps zip: 2f6a93654d1cfe191ff709b360ad60fc
For the su zip: b23147cb55eba3ae32a996a913fa54ea
I'm too new to the forum to post the link where I'm getting my instructions.
The CM7 version is update-cm-7.0.3-N1-signed, the RA is recovery-RA-passion-v2.2.1, the radio img is Radio_20100203_2_Signed_PASSION (the updated radio link you posted had removed the radio img because of some sort of violation), and gapps zip is gapps-passion-ERE36B-2-signed.
Still having the bootloop problem. I tried to find the most updated versions of everything I could. Is there a compatibility issue somewhere?
Another thought:
Do I need to flash the su zip from my sdcard in recovery? I don't know what that will do, so I haven't tried it yet.
There are a couple of files that Amon-RA suggests I delete in order to prevent calling the stock recovery:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
Any idea how I can check for and delete these using fastboot via mac terminal?
You can't delete them from fastboot. Use fastboot to boot off the new recovery and delete them in there through adb.
Code:
fastboot boot recovery "c:\location\to\recovery.img"
Can you be more specific? I use fastboot to flash the recovery image, and when I'm in recovery on the phone, I use adb from my computer? Or I can access a command line in the phone?
Well, you use fastboot to flash the recovery. Then you use the command I posted below so you can boot directly into that recovery. Once in there, you use adb on the computer to go into the phone, mount the system partition (which can be done under the mounts and storage menu in recovery) and then find those files and remove them.
But you really only need to delete those files if you want to stay running stock Android. If you have a custom recovery on the phone, that is all you need to install CM, and CM doesn't contain the files that revert the recovery back to stock.
Just got it to work. It was, in fact, a compatibility issue. The gapps zip was for a different version. I found a different zip (for Gingerbread) at: http://goo-inside.me/gapps. If you have Gingerbread, choose a zip with gb in the name.
Related
Right, can someone give me a quick set-by-set of what to do from my position.
I can access HBOOT fine (HBOOT-1.33.2005 / RADIO-2.22.23.02) and i can access my System Recovery fine (RA-dream-v1.7.0), but i can't boot to my Rom.
I have the following on my desktop:
HBOOT-1.33.0013d
RADIO-2.22.27.08
gapps-tiny-112010 (that the right one?)
froyobylaszlo-5.1 (from: http://forum.xda-developers.com/showthread.php?t=929678)
If my thinking is right, i need to:
- Delete the rom etc. that i installed wrong
- Move the files from my desktop onto my SD
- Install everything
- Boot
However, i'm not sure how to go about that... So this is where i need the simple instructions and advice.
**There was a serial0 question before, so ignore the first few posts.
Seems it's because i was using RC29 instead of RC7...
Soon as my phone has charged, i'll flash the rom
New issue:
Need some help people. Rooted my G1, worked. Got it back to 1.5, then updated it all. Installed the Recovery.img and that worked. Now, i want to install this:
http://forum.xda-developers.com/showthread.php?t=929678
But im not sure what radio, SPL and gapps to use. I followed this video:
http://www.youtube.com/watch?v=DR0HpUVv-BY
Then when he installed Cyanogen, i installed Gingerbread. Now im stuck on the boot screen and have been for 2 hours... ideas?
I'm thinking the files i used, from the video, ain't compatible. So, anyone have links to "SPL: 1.33.0013d (hboot)" and "RADIO: 2.22.27.08 / 28.25"? Then, what do i do from the Recovery screen to delete all i did and install Gingerbread?
wow you are in a rush to take the G1 all the way to the hilt arent ya?
What roms have you successfully run on it prior (if at all) to trying to flash Lazlo? Did Eclair work?
I ran Cyanogen6 for a long while till it developed a slight lag. In all i've ran:
Cyan6, then 1.6, then Cyan6, then 1.6 again, now im trying this.
I created the 3 - 4 Partition, THEN the 2 - 3 Partition.
Think that could be the issue?
If so, how do i go back and try again?
**NEW QUESTION FROM HERE
dmreall said:
Right, can someone give me a quick set-by-set of what to do from my position.
I can access HBOOT fine (HBOOT-1.33.2005 / RADIO-2.22.23.02) and i can access my System Recovery fine (RA-dream-v1.7.0), but i can't boot to my Rom.
I have the following on my desktop:
HBOOT-1.33.0013d
RADIO-2.22.27.08
gapps-tiny-112010 (that the right one?)
froyobylaszlo-5.1 (from: http://forum.xda-developers.com/showthread.php?t=929678)
If my thinking is right, i need to:
- Delete the rom etc. that i installed wrong
- Move the files from my desktop onto my SD
- Install everything
- Boot
However, i'm not sure how to go about that... So this is where i need the simple instructions and advice.
**There was a serial0 question before, so ignore the first few posts.
Click to expand...
Click to collapse
froyobylaszlo-5.1 needs radio 2.22.27.08/2.22.28.25,spl 1.33.0013d,flash your radio&spl first
Got Cyanogen6 working on it now.
I downloaded HBOOT-1.33.0013d and RADIO-2.22.27.08, zipped them, then moved them onto my SD card and when i try flash them on my G1, it's says invalid file.
dmreall said:
Got Cyanogen6 working on it now.
I downloaded HBOOT-1.33.0013d and RADIO-2.22.27.08, zipped them, then moved them onto my SD card and when i try flash them on my G1, it's says invalid file.
Click to expand...
Click to collapse
have u tried the guide from here to update your radio and spl
(p/s u need to follow it properly and understand most of the jargons such as spl perfect or engineered and etc)
http://forum.xda-developers.com/showthread.php?t=831139
Ok, so going by that i need to:
- Put them files onto my SD (not zipped, just as they are downloaded and into the root)
- Boot into fastboot
- Enter Console and type:
Code:
fastboot flash recovery recovery-RA-dream-v1.7.0-cyan.img
fastboot flash radio radio-2.22.27.08.img
fastboot flash hboot hboot-1.33.0013d.img
fastboot reboot-bootloader
- Check it says "1.33.0013d" as its version
- Enter console again and type:
Code:
fastboot erase system -w
fastboot erase boot
- Restart
- Boot to Recovery
- Go to "Flash"
- Select "Froyo by Laszlo"
- Reboot
Am i right with that method?
Need to know before i risk it
Just install yoshi ginger its so smooth (gingerbreab 2.3)
sent from my gingerdream
dmreall said:
Am i right with that method?
Need to know before i risk it
Click to expand...
Click to collapse
In theory it is already right. Maybe some small litte details.
After fastboot erase(before flashing rom), u should partition your sdcard so that it has the ext4 partition ( from recovery, partition sd, follow steps, upgrade from ext2 to ext3, upgrade ext3 to ext4 )
After that try using the wipe and reset all data to factory.
Now maybe u are good to go with flashing roms.
For the radio/hboot guide, just follow step by step from the thread.
This better then? I just want to make a guide for the future.
- Put "Recovery", "Radio" and "HBOOT" files onto SD (not zipped and into the root)
- Boot into fastboot
- Enter Console and type:
Code:
fastboot flash recovery recovery-RA-dream-v1.7.0-cyan.img
fastboot flash radio radio-2.22.27.08.img
fastboot flash hboot hboot-1.33.0013d.img
fastboot reboot-bootloader
- Check it says the Hboot that was just flashed as its version
- Enter console again and type:
Code:
fastboot erase system -w
fastboot erase boot
- Restart
- Boot to Recovery
- Go to "Partion SD"
- Partition SD with "Swapsize = 96" and "Ext2 = 1024" then "Ext2 to Ext3" then "Ext3 to Ext4"
- Go to "USB MS Toggle"
- Move Rom onto SD
- Go to "Flash"
- Select the ROM to flash
- Reboot
Click to expand...
Click to collapse
looks quite good, do u want to make a guide for the forum or just for urself?
If for the forum, maybe just add some small details as example :
boot into recovery ( hold power + home together )
Just for the new people without experiences in flashing.
No, this is for myself. Just trying to get a solid method i can reference to whenever im stuck.
Fastboot is "Power + Camera" yes? If so, i don't see a console.
Still need that one answered.
Also, should i put the files as .img or .zips in the root of my SD?
Fastboot can be accessed with camera and power or back and power.
You would move the files as zips.
A couple of notes. I wouldn't upgrade to ext4 as not all roms work with 4 (most do but not all) just go to ext3 and you will be good. If it supports ext4 then it will 3 also.
Also most of your guide is really only needed for the first time. if you are just switching roms you don't need to do half of that.
If just switching roms you only need to boot to recovery, wipe/factory reset, flash/install zip (depending on what the recovery calls it its the same thing). Reboot and enjoy.
Android G1 mobile software required (urgent)
Hi,
I have Htc G1 android mobile set.
The problem is my mobile phone only goes till G1 logo and does not proceed forward.
I think i have to flash my mobile set using micro SD card.
Can anyone plz share with me android G1 software and the method to do that.
I shall be grateful.
Regards,
Khurram
Hello All,
I am a noob and recently learned how to root, unlock or re-partition, install blackrose etc but using your blogs and wikicynogemod.
I am trying to update my phone to Texas ICS using blog by OP- http://forum.xda-developers.com/showthread.php?t=1366897
I was able to reach till the step mentioned below :
i.e.
fastboot flash hboot hboot_brcrust_220-10-206-ICS.nb0
fastboot reboot-bootloader
fastboot -w
and now my phone shows TexasICS on the second line that mans it flashed correctly.
I downloaded the tar file "Evervolv-Perdo-2.2.0a6" but I am clueless about the next steps.
1. To build Evervol --> How and where as repo command doesnt work on my computer undert android sdk directory
2. tar xjf --> I am using windows 7 and hence no tar on my laptop.Meanwhile I am downloading the zip file also and see if unzip works.
But I am curious where to run these commands- either on cmd prompt under android-sdk directory or the phone emulator.
And interestingly, android-sdk dont have unzip/tar command and I have no access to phone now, its not booting.
Also I cant login to my phone now, when I boot it, its stuck at the Nexus One startup logo, not going further, so I believe I can't put anything in the SD card now.
Kindly help as my phone is not accessible now and I am kind of handicapped because of that
FYI : Recently I upgraded the phone to 2.3.7 using Cynogenmod, clock recovery.
you might have lost ur recovery
so fastboot any preffered recovery.img . put .zip in sd and flash it
or you can fastboot system.img, boot.img n recovery.img
Sent from my Nexus One using Tapatalk
If you have a custom recovery like clockworkmod just turn on your device holding trackball or something (I don't remember exactly) and you'll be in recovery or fastboot. Anyway, go to recovery and restore your nand backup. After that you can keep trying (or read below).
If you don't have a backup you can insert the SD card directly into the computer and copy the Evervolv latest version (.ZIP). Then go to recovery and wipe data & cache then install the zip from sd card.
You don't need to pay attention to the building Evervolv part of the post as it's not needed for the install. Don't forget to flash gapps later if you want to.
Sorry for my English and I hope this helps as I'm a bit noob also
Sent from my GT-P7510 using xda app-developers app
flash recovery
Flash recovery by
booting in fastboot
fastboot flash recovery recoveryNAME.img
then reboot to recovery u will get recovery the flash ICS.zip rom
Hello
I've tried installing guestekrnL on WIUI. When installing guestekrnL, the only thing I've ticked extra that was other than defaults was:
"Activate init.d functionality and convert file system to EXT4?
- yes
select if init.d is not working yet or if you don't know"
Well, after reboot WIUI was screaming that my sd card is broken and format may help. It formatted it, but it still didn't work. So I've rebooted to recovery via option in power dialog in order to restore old firmware. However there's a problem now: CWM Touch says that it can't write logs to /cache. Mounting /cache, /data or /emmc from recovery doesn't work, only /system and /sdcard are mounting correctly. I've tried BackToExt3 with no luck. I've tried wiping it many times, with no luck. My phone only boots now to CWM. I can't flash stock via APX mode, because I have broken USB port in my phone. What can I do?
Does restoring a backup, flashing a zip file or wiping work?
Ok, I was searching for almost whole hour now and it seems it's a problem with partition table. Fixing can be done via zip, but I need some dumps. First one from "cat /proc/mounts" and second from "parted".
Here's the zip for nook color if someone wants to do that for me: http://forum.xda-developers.com/showthread.php?t=1759558
exinepl said:
Ok, I was searching for almost whole hour now and it seems it's a problem with partition table. Fixing can be done via zip, but I need some dumps. First one from "cat /proc/mounts" and second from "parted".
Here's the zip for nook color if someone wants to do that for me: http://forum.xda-developers.com/showthread.php?t=1759558
Click to expand...
Click to collapse
the Touch CWM might be the issue......most of the times it is found as the source of some unknown issues for some or intermittent issues.
I use the non-touch one always
Hope it helps
Well, how do I flash new recovery from CWM using zip then?
exinepl said:
Well, how do I flash new recovery from CWM using zip then?
Click to expand...
Click to collapse
check for the CWM thread by Rusty....you have the instructions and process in it.
THERE YOU GO>>>SEE HERE
Hope it helps
Unfortunately, it needs USB. I need to flash it via existing recovery.
Mounting problems occur on some zips using touch recovery . Change cwm to non touch 5.0.2.8. But hey, did you flash a stock kernel on wiui ? you need another kernel, like etana, symbiosis.....or just use the one shipped with rom
**Disclaimer** If you don't understand what follows, don't attempt this. I'm not responsible for you softbricking your device,
This is a quick guide for how to install the new android without losing anything. You'll need fastboot for this. Also, before doing this, be sure to download the supersu cwm update zip, and have it on your sdcard. Make sure you also already have a custom recovery installed (I did twrp, but i'm sure cwm will work just as well). I would also suggest having a backup done, through titanium backup and through recovery, just incase.
First, download the factory images for the n7 from google's website. Decompress them (if you're in windows, you'll need winrar or something similar.) After you decompress the archive, there'll be another one inside (image-nakasi-jop40c.zip), decompress this one as well. Under here, you'll see the .img files for all the partitions. For now, go up one directory. You'll also see here bootloader-grouper-4.13.img. Once you have all this, reboot into the bootloader.
Once you're in the bootloader, you can update the bootloader to the new version (this step isn't needed, but I did it anyways). Plug into your pc, and type fastboot devices. Make sure it's not blank. If it is, you have to update drivers. If you can see the device, open up a command prompt, and cd to the directory that has the bootloader-grouper file. Type the following:
fastboot flash bootloader-grouper-4.13.img
then, after it's done, type:
fastboot reboot-bootloader
Now, you'll be booted back into the bootloader, it'll say 4.13. On to the rom.
cd into the folder image-nakasi-jop40c (make sure you see the files system.img and boot.img before you continue. If you don't see them, the next steps will do nothing but erase your kernel and system parition.)
now, you see the image files. Type the following (still in the bootloader)
fastboot erase system
fastboot flash system system.img
wait until it completes, then type:
fastboot erase boot
fastboot flash boot boot.img
Once this is done, hit the volume up on the device until it shows recovery mode on the top. When it does, push the power key and you'll boot into your recovery (shouldn't be touched.) Inside here, flash the supersu cwm zip file, which'll flash the superuser binary, and supersu. Once this is done, do a factory reset (removing your data and cache.) Boot into the rom.
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
My first boot got stuck for some reason. if it happens to you, just hold the power button and hard reboot. (I did this on 2 devices, it only happened to one of them, so I figured I'd give you all warning.)
Links:
SuperSu binary: https://docs.google.com/open?id=0B7a8xHNJlpgTR0ZkR1pWZWR2VzA
Google Factory Images: https://developers.google.com/android/nexus/images
Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?
Thanks for this.. Apparently you found out too a clean 4.2 isn't rootable via typical methods.
That SuperSU package did the trick. I have to remember to keep a SuperSU binary on hand for these kinds of situations that SuperUser fails..
jefferson9 said:
Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?
Click to expand...
Click to collapse
Yes. If you do it though cwm, you're not using any exploits, you're just inserting the superuser binary and supersu.apk into the proper places on the rom. On any nexus device, any rom, this will root it.
mstrk242 said:
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place.
Click to expand...
Click to collapse
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.
tehSmoogs said:
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.
Click to expand...
Click to collapse
Exactly.
If everything goes right we should have an AOSP prerooted build in about *looks at watch* 20 minutes.... Unless there is a compile error or SU error. *laff*
Back to watching the scrolling terminal window
Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!
kwhee07 said:
Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!
Click to expand...
Click to collapse
I did this all on linux, just kind of adapted the guide for windows. I figured all the linux users would understand how to do it on their own. Glad to know it's the same for mac as well.
OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/
rootbrain said:
OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/
Click to expand...
Click to collapse
Settings - about tablet - build number
push it a few times and it will enable dev options
You have .bat file in the package.
Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...gned-nakasi-JOP40C-from-JZO54K.094f6629.zipia
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.
Here is my method:
1. Download official 4.1.2 from http://forum.xda-developers.com/showthread.php?t=1929270 and 4.2 OTA image from http://forum.xda-developers.com/showthread.php?t=1989188
2. Boot into CWM (i have CWM touch installed)
3. Clear data and install 4.1.2, don't forget to turn on root in the installer
4. reboot check that root is fully working
5. reboot into recovery install 4.2
6. before reboot CWM will ask to disable recovery flash and protect root. Ansver yes to both questions
I'm confused, it says if you are already on a custom rom, just flash as usual.
What makes this different?
I was on stock ROM rooted with some system modifications, and this wwadd the only way I could get the update working...
Sent from my Nexus 7 using xda app-developers app
mstrk242 said:
For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
Click to expand...
Click to collapse
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.
Ill have to wait until a rooted rom is created, I have no comp.
Sent from my Nexus 7 using XDA Premium HD app
can I install image-nakasi-jop40c.zip directly without upgrading bootloader?
Zuk. said:
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.
Click to expand...
Click to collapse
Not advisable to move this folder - if it got moved to a new location by the o/s then there's probably a good reason why - maybe like 4.2 introducing multiple users
Each user appears to get their own "home" directory created in /mnt/shell/emulated/
Default user dir is "0"
Second user dir is "10"
Each contain the standard dir's from 4.1 and earlier.
Travelawyer said:
Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...signed-nakasi-JOP40C-from-JZO54K.094f6629.zip
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.
Click to expand...
Click to collapse
You had two extra characters at the end of your link, but I fixed it above and it's good to go for others in the future. Just flashed it in TWRP, it didn't ask if I wanted to maintain root, hit reboot when it was complete and lost root, so it doesn't work for everyone - good news is that all my data remained intact without having to resort to advanced restoring my data from a backup....
When I tried the SuperSU binary root flash trick, I finally got root back. But don't think it's as easy to get to recovery! I had to obtain the TWRP Recovery one more time since it wiped it and put in place a recovery that did absolutely nothing but reboot the device after a few minutes, so you'll have to
Code:
fastboot flash recovery openrecovery-twrp-2.3.1.1-grouper.img
to get TWRP back.... Hope that helped everyone!
I am just new to this flashing custom roms or firmware and twrp also. And dumb enough to not back it up.
I wanted to install arrow os in my phone. When I was about to wipe data, cache and dalvik, I accidentally checked metadata also and wiped. Then problems created more problems.
problems right now:
I cant put a file in my storage
Internal Storage is just blank on my pc
No OS
TWRP on both slots
please help me i really needed help and knowledge about it
I hope the attachment helps
EDIT--
Solutions to my problems:
WHEN you softbrick your phone and you only have fastboot and nothing else
Thanks to this guy..
SOLUTION: download your original firmware but choose the fastboot one and not recovery after download just unzip. Double click flash_all.bat and its back to square one.
WHEN you dont know how to flash or the file you have is .img
SOLUTION: find a guide in xda because apparently you can install a .img file in "fastbootd" mode
the guides here: https://forum.xda-developers.com/t/...sues-all-without-any-custom-recovery.4337099/
COMMENT: not the usual thats what on top of youtube search.
WHEN you see errors in twrp/orangefox recovery you might get panic and search for solution.
COMMENT: try to find and use a solution that doesnt delete something first. In my experience it got bricked even more.
Thanks to the people who commented back on my post and helping me get to know what to do next.
Try putting the stock ROM on a SD card or usb (if you have a dongle).
georg3_ said:
Try putting the stock ROM on a SD card or usb (if you have a dongle).
Click to expand...
Click to collapse
SD card that you put on beside the sim? if yes
Do I download stock ROM in official website? Cus I dont have 1 right now
then flashing it there by using twrp? is that how its gonna run? because i really dont wanna assume and create another problem
Try flashing this stock ROM (global) from a SD card, in TWRP. It's a recovery package, so you can install it as any zip.
Also, can you boot into fastboot/bootloader from TWRP?
Plus, where did you get the ArrowOS image? There are no builds, official or not.
georg3_ said:
Plus, where did you get the ArrowOS image? There are no builds, official or not.
Click to expand...
Click to collapse
I found it here
It is made my myst33d and it is a beta build
im getting a sd card right now to test it out
And yes I still can go to fastboot/bootloader from twrp
I cant seem to find my file in twrp... even in file manager
the file is int .tgz must I change it to .zip?
raikiro1 said:
I cant seem to find my file in twrp... even in file manager
Click to expand...
Click to collapse
Is the twrp detecting your sd card?try click on the Install image and change to install zip
can you sideload?
I can now see it, I think I reflashed twrp, now I can, but I cant install because of failed to mount system_root and I have done change file system of data to Ext4. when it resets it comes back to f2fs
edit: change file system of data to Ext4 failed
edit2: thank you guys really for commenting back and helping me
is no verity affecting it? cus I am not able to install it now
you should format data and put the arrow build in it, maybe it will work
J6idot said:
you should format data and put the arrow build in it, maybe it will work
Click to expand...
Click to collapse
I have changed the data to Ext4, fomarted, wiped again the data,dalvik and cache
I have a Redmi Note 10S Rosemary from xiaomiupdater but I still cannot install the rom cus there is a error " Error installing zip file /sdcard1/thefile."
I tried to install no verity opt encrypt but failed and says updater process ended with ERROR: 1
Error installing zip file "sdcard1/thefile"
raikiro1 said:
I cant seem to find my file in twrp... even in file manager
the file is int .tgz must I change it to .zip?
Click to expand...
Click to collapse
Must change it to zip.
EDIT: Extract the file, there's a zip or img inside.
raikiro1 said:
I have changed the data to Ext4, fomarted, wiped again the data,dalvik and cache
I have a Redmi Note 10S Rosemary from xiaomiupdater but I still cannot install the rom cus there is a error " Error installing zip file /sdcard1/thefile."
I tried to install no verity opt encrypt but failed and says updater process ended with ERROR: 1
Error installing zip file "sdcard1/thefile"
Click to expand...
Click to collapse
Try to sideload it, maybe it'll work.
georg3_ said:
Must change it to zip.
Click to expand...
Click to collapse
Should have said "extract the file, there's a zip or img inside", don't change the file extension.
Update: I found the guide how to sideload ... just change the Ext4 to F2fs
[Tutorial] TWRP ADB Sideloading
Alternative solution: OTG usb flash drive - With one of these, you can store a ROM zip safely, and still format ‘userdata’ to f2fs or EXT4. TWRP ADB Sideloading Requirements: Mac | Linux | Windows PC / Laptop and TWRP Custom Recovery Moto G...
forum.xda-developers.com
and I was able to sideload it and then got MIUI finally
what worried me is there were still errors like system_root, vendor and product... and its running fine now I guess but im back on track to make it to arrow OS.... I hope no mistakes this time like deleting metadata.
Thank you all who replied to this post , I really do. Thank you
raikiro1 said:
Update: I found the guide how to sideload ... just change the Ext4 to F2fs
[Tutorial] TWRP ADB Sideloading
Alternative solution: OTG usb flash drive - With one of these, you can store a ROM zip safely, and still format ‘userdata’ to f2fs or EXT4. TWRP ADB Sideloading Requirements: Mac | Linux | Windows PC / Laptop and TWRP Custom Recovery Moto G...
forum.xda-developers.com
and I was able to sideload it and then got MIUI finally
what worried me is there were still errors like system_root, vendor and product... and its running fine now I guess but im back on track to make it to arrow OS.... I hope no mistakes this time like deleting metadata.
Thank you all who replied to this post , I really do. Thank you
Click to expand...
Click to collapse
no problem next time installing, stick to sideloading, less room for error
I cant seem to install TWRP recovery again it justs bootloop .. I dont know why anybody knows?
Whenever I fastboot boot twrp3.6.1-rosemary it fails, says too many links, and when I fastboot reboot recovery it boot loops
flashboot flash boot twrprosemary says okay in slot A and I even put it to B and flash it there sadly
the problem might be because its A12 ... just an update
raikiro1 said:
I cant seem to install TWRP recovery again it justs bootloop .. I dont know why anybody knows?
Whenever I fastboot boot twrp3.6.1-rosemary it fails, says too many links, and when I fastboot reboot recovery it boot loops
flashboot flash boot twrprosemary says okay in slot A and I even put it to B and flash it there sadly
the problem might be because its A12 ... just an update
Click to expand...
Click to collapse
A12 shouldn't be a problem.
Probably you should flash another vbmeta.img.
OR
I don't know if there is an .img twrp around, but if there is you can:
Code:
fastboot boot {recovery.img}
and then [Advanced]>[Install Recovery Ramdisk].
raikiro1 said:
I cant seem to install TWRP recovery again it justs bootloop .. I dont know why anybody knows?
Whenever I fastboot boot twrp3.6.1-rosemary it fails, says too many links, and when I fastboot reboot recovery it boot loops
flashboot flash boot twrprosemary says okay in slot A and I even put it to B and flash it there sadly
the problem might be because its A12 ... just an update
Click to expand...
Click to collapse
what vbmeta are you using?