Related
As the name implies this the unsecure stock kernel boot.img
You can use the adb remount command to push files to system now!
YOU MUST HAVE AN UNLOCKED BOOTLOADER FOR THIS! See here for more info: http://forum.xda-developers.com/showpost.php?p=30274025&postcount=317
If you dont know what this then it may not be for you. This is more so developers can use in there ROMS.
No need to ask to use it, just give credit if you do.
Download HERE
Chang Log
v3 - Corrected incorrect adbd in /sbin for proper colors when using screen capture while in Dalvik Debug Manager.
v2 - Added Lib folder for that need it.
New clean ROM soon then?
Sent from my SCH-I535 using xda app-developers app
Would it be too much to ask for an AOSP kernel (ICS)? I'd do it myself, but I don't know much about kernels lol
Nopi45 said:
New clean ROM soon then?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Well, this is more for developers.
It just unlocks the /system partition so you can push files. I mean, yeah, it will be in the next CleanROM but its not urgent from a user perspective.
PureMotive said:
Would it be too much to ask for an AOSP kernel (ICS)? I'd do it myself, but I don't know much about kernels lol
Click to expand...
Click to collapse
This is a Stock kernel. I just modified the RAM Disk to remove security and to add init.d support and set up the script so it can be flashed.
I didint build the kernel. Its just stock.
How come your user name is in italics BTW?
Not sure on run parts... Need to check. Unsecure is still a go!
scrosler said:
This is a Stock kernel. I just modified the RAM Disk to remove security and to add init.d support and set up the script so it can be flashed.
I didint build the kernel. Its just stock.
How come your user name is in italics BTW?
Click to expand...
Click to collapse
I know it's stock. I was just wondering whether you were able to get an unsecured AOSP kernel for all of the AOSP ROMs out there. It'd also help with Sense 4.
To get your username in italics (RDs only):
Go to User CP
Select "Group Membership" from the side bar
Select "Recognized Developer - Identify me as a member of this group"
Save
Well this work on lf2?
Neverendingxsin said:
Well this work on lf2?
Click to expand...
Click to collapse
Are you a dev?
No?
Keep moving
VERIZON GALAXY S 3
PureMotive said:
I know it's stock. I was just wondering whether you were able to get an unsecured AOSP kernel for all of the AOSP ROMs out there. It'd also help with Sense 4.
To get your username in italics (RDs only):
Go to User CP
Select "Group Membership" from the side bar
Select "Recognized Developer - Identify me as a member of this group"
Save
Click to expand...
Click to collapse
To make it unsecure its just some changes in the RAM Disk. Im sure if the AOSP guys are out they know how to do that. If not they can reach out to me for help but they tend to know more than I do about kernels and all
Thanks for the heads up the italics!
Neverendingxsin said:
Well this work on lf2?
Click to expand...
Click to collapse
DROID3R said:
Are you a dev?
No?
Keep moving
VERIZON GALAXY S 3
Click to expand...
Click to collapse
Click to expand...
Click to collapse
This is mostly for developers that want to do things that having a locked boot.img normally stops you from doing. An average user will gain little value...
But lets say you were making a theme and had to "push" files to the /system folder you can NOW do that with this boot.img. It makes Dev's lives a LOT more easy now, lol
scrosler said:
To make it unsecure its just some changes in the RAM Disk. Im sure if the AOSP guys are out they know how to do that. If not they can reach out to me for help but they tend to know more than I do about kernels and all
Thanks for the heads up the italics!
This is mostly for developers that want to do things that having a locked boot.img normally stops you from doing. An average user will gain little value...
But lets say you were making a theme and had to "push" files to the /system folder you can NOW do that with this boot.img. It makes Dev's lives a LOT more easy now, lol
Click to expand...
Click to collapse
yes it does, copying files to my sdcard and then moving them with root explorer, or packaging them in a flashable zip and copying to sdcard and flashing everytime is frustrating. specially if your doing it every 10-15 mins.
nosympathy said:
yes it does, copying files to my sdcard and then moving them with root explorer, or packaging them in a flashable zip and copying to sdcard and flashing everytime is frustrating. specially if your doing it every 10-15 mins.
Click to expand...
Click to collapse
Tell me about man, tell me about it!
And I confirmed init.d support is functional as well!
I know this is just a simplification process for devs and it helps skip the extra step of moving files somewhere else first then move to /system with root explorer if you're rooted, so please don't ask if I'm a dev, the answer is: no, I'm not. I would appreciate if someone could only answer this question without getting into other details. I would like to know if it would harm or break anything if I have VRALF2 rom and radio/stock kernel and I flash a VRALG1 kernel, but keep the rest as it is? Would this newer kernel work with my older version rom, or do I have to flash the whole package first? I basically don't want to renew my rom to the new G1 version since there is no apparent improvement (it's actually worse) over the older F2 version rom, since it downgrades certain things.
Thanks
newuser134 said:
I know this is just a simplification process for devs and it helps skip the extra step of moving files somewhere else first then move to /system with root explorer if you're rooted, so please don't ask if I'm a dev, the answer is: no, I'm not. I would appreciate if someone could only answer this question without getting into other details. I would like to know if it would harm or break anything if I have VRALF2 rom and radio/stock kernel and I flash a VRALG1 kernel, but keep the rest as it is? Would this newer kernel work with my older version rom, or do I have to flash the whole package first? I basically don't want to renew my rom to the new G1 version since there is no apparent improvement (it's actually worse) over the older F2 version rom, since it downgrades certain things.
Thanks
Click to expand...
Click to collapse
When you say no improvement are you talking the Modems? If you are only flashung a rom and havent changed the kernel then it would be the same as just flashing the g1 modem with a different rom correct.
Hey scrosler how can I identify that the flash worked. The ROM booted normally but in the kernel name I don't see any change.
wooddale said:
When you say no improvement are you talking the Modems? If you are only flashung a rom and havent changed the kernel then it would be the same as just flashing the g1 modem with a different rom correct.
Click to expand...
Click to collapse
I'm not talking about the modem, I'm asking about the kernel, if I flash THIS unsecure (G1) kernel, but otherwise have ALL F2 stuff (modem, rom, etc), will it mess up anything? I think u misunderstood my question, I don't want to flash a G1 rom or modem, just the kernel, because the modems are same, so no improvement there, and the F2 rom is better than the G1 rom, so I'm keeping everything as F2 like it was, but flashing this G1 kernel. Will that be compatible/ok?
Try it??? If it fails just restore from backup?
Sent from my Nexus 7 using Tapatalk
newuser134 said:
I'm not talking about the modem, I'm asking about the kernel, if I flash THIS unsecure (G1) kernel, but otherwise have ALL F2 stuff (modem, rom, etc), will it mess up anything? I think u misunderstood my question, I don't want to flash a G1 rom or modem, just the kernel, because the modems are same, so no improvement there, and the F2 rom is better than the G1 rom, so I'm keeping everything as F2 like it was, but flashing this G1 kernel. Will that be compatible/ok?
Click to expand...
Click to collapse
I tried this out and did not see ANY difference. But then again it's midnight and I won't know if anything will be wonky until I use it at work tomorrow
sent from a locked downloader
newuser134 said:
I know this is just a simplification process for devs and it helps skip the extra step of moving files somewhere else first then move to /system with root explorer if you're rooted, so please don't ask if I'm a dev, the answer is: no, I'm not. I would appreciate if someone could only answer this question without getting into other details. I would like to know if it would harm or break anything if I have VRALF2 rom and radio/stock kernel and I flash a VRALG1 kernel, but keep the rest as it is? Would this newer kernel work with my older version rom, or do I have to flash the whole package first? I basically don't want to renew my rom to the new G1 version since there is no apparent improvement (it's actually worse) over the older F2 version rom, since it downgrades certain things.
Thanks
Click to expand...
Click to collapse
Well, you can try it but my experieince tells me that you may loose LTE and WiFi because yo dont have matching modules. The modules (aka drivers if it were windfows) hare specific to a kernel. If you took the /system/lib/modules folder from a G1 ROM like mine or nosympathy and pushed them in I bet it would work just fine. But why on earth are you on older build?
wooddale said:
When you say no improvement are you talking the Modems? If you are only flashung a rom and havent changed the kernel then it would be the same as just flashing the g1 modem with a different rom correct.
Click to expand...
Click to collapse
No, Gerneally ROMS dont include the radios from my experience. BUt I heard int he samsung world Devs do things differently so I dont honestly now.
jb_alphamale said:
Hey scrosler how can I identify that the flash worked. The ROM booted normally but in the kernel name I don't see any change.
Click to expand...
Click to collapse
Thats easy... Before you flashed the boot.img was USB deggign turned on? If not it would be turned on now.
If USB degging was already on or not on turn it on... Then... connect phone and wait for the connection to finish. Then type "adb remount" (assuming you have ADB handy) and it should say "remount succeeded" If it says operation not permitted then it did not take.
newuser134 said:
I'm not talking about the modem, I'm asking about the kernel, if I flash THIS unsecure (G1) kernel, but otherwise have ALL F2 stuff (modem, rom, etc), will it mess up anything? I think u misunderstood my question, I don't want to flash a G1 rom or modem, just the kernel, because the modems are same, so no improvement there, and the F2 rom is better than the G1 rom, so I'm keeping everything as F2 like it was, but flashing this G1 kernel. Will that be compatible/ok?
Click to expand...
Click to collapse
Hipcatjack said:
I tried this out and did not see ANY difference. But then again it's midnight and I won't know if anything will be wonky until I use it at work tomorrow
sent from a locked downloader
Click to expand...
Click to collapse
What difference did you expect? Its a STOCK kernel and will behave like a stock kernel except give full and true root access to the device. Its not for the end user its for developers. Of course this ramdisk will also allow us to start modifying and shutting off services, tweak things at the kernel level, etc... But right now, this is just bone stock with init.d support and root level access to the file system via ADB.
Hope that explains it some.
hey all
after unlocking bootloader and rooting , now i can't flash any roms because it will stuck on boot animation , SO any one has KK CWM or TWRP backup for GLobal Version to go back to working phone ? i will not flash any thing anymore .
really Appreciated .
I have one, although I'm not entirely sure it'll work?
What about any privacy issues regarding my information?
I'll try and do a backup, then wipe my phone and then do another backup so you get a clean version, okay?
Edit: I don't exactly know how to share the backup. Can I just connect phone to laptop and upload here as is?
Sent from my XT1034 using Tapatalk
Jwtiyar said:
hey all
after unlocking bootloader and rooting , now i can't flash any roms because it will stuck on boot animation , SO any one has KK CWM or TWRP backup for GLobal Version to go back to working phone ? i will not flash any thing anymore .
really Appreciated .
Click to expand...
Click to collapse
I think you are better off just restoring it to factory fresh yourself. It doesn't take long at all just find the correct stock ROM and use fastboot. Here is a guide, http://forum.xda-developers.com/showthread.php?t=2542219 it seems complicated, I skipped most of the explanation and just used Fastboot using the commands in 3b).
Here follows a simpler version.
http://techtrickz.com/how-to/unroot-moto-g-and-return-to-box-fresh-state-guide/
I myself went back to stock, but left it rooted so that I can make backups. I need a ROM which supports the Motorola magnetic flip cover, couldn't find one, so gave up for now. As to your getting stuck on boot animation, I had the same trouble until I used TWRP ver 2631
Jwtiyar said:
hey all
after unlocking bootloader and rooting , now i can't flash any roms because it will stuck on boot animation , SO any one has KK CWM or TWRP backup for GLobal Version to go back to working phone ? i will not flash any thing anymore .
really Appreciated .
Click to expand...
Click to collapse
Here is a cwm 4.4.2 gb backup : https://www.dropbox.com/s/zkynj8eacnlmucb/1970-01-02.18.49.56.zip
It should be a clean backup without any information from previous phone. That's not mine. All credits to Nent.
S0bes said:
Here is a cwm 4.4.2 gb backup : https://www.dropbox.com/s/zkynj8eacnlmucb/1970-01-02.18.49.56.zip
It should be a clean backup without any information from previous phone. That's not mine. All credits to Nent.
Click to expand...
Click to collapse
Thank you very much appreciate it .
KabelGuy said:
I have one, although I'm not entirely sure it'll work?
What about any privacy issues regarding my information?
I'll try and do a backup, then wipe my phone and then do another backup so you get a clean version, okay?
Edit: I don't exactly know how to share the backup. Can I just connect phone to laptop and upload here as is?
Thank youu very much i will try S0bes backup.
Sent from my XT1034 using Tapatalk
Click to expand...
Click to collapse
Sent from my XT1032 using Tapatalk
grahamgo said:
I think you are better off just restoring it to factory fresh yourself. It doesn't take long at all just find the correct stock ROM and use fastboot. Here is a guide, http://forum.xda-developers.com/showthread.php?t=2542219 it seems complicated, I skipped most of the explanation and just used Fastboot using the commands in 3b).
Here follows a simpler version.
http://techtrickz.com/how-to/unroot-moto-g-and-return-to-box-fresh-state-guide/
I myself went back to stock, but left it rooted so that I can make backups. I need a ROM which supports the Motorola magnetic flip cover, couldn't find one, so gave up for now. As to your getting stuck on boot animation, I had the same trouble until I used TWRP ver 2631
Click to expand...
Click to collapse
Thanks but its really complicated .
Sent from my XT1032 using Tapatalk
Here is another tool that I came across. Its an active posting in its 2nd or 3rd iteration, but it looks like it simplifies things quite a bit.
http://forum.xda-developers.com/showthread.php?t=2631030
grahamgo said:
Here is another tool that I came across. Its an active posting in its 2nd or 3rd iteration, but it looks like it simplifies things quite a bit.
http://forum.xda-developers.com/showthread.php?t=2631030
Click to expand...
Click to collapse
Thank you very much , i tested it yesterday work great.
Sent from my XT1032 using Tapatalk
grahamgo said:
Here is another tool that I came across. Its an active posting in its 2nd or 3rd iteration, but it looks like it simplifies things quite a bit.
http://forum.xda-developers.com/showthread.php?t=2631030
Click to expand...
Click to collapse
Thank you very much , i tested it yesterday work great.
Sent from my XT1032 using Tapatalk
Hello everyone, I have a tablet that is stuck in recovery and looks to me ADB is going to be the only way out here. Problem is ADB isnt recognizing my device, device manager named it MTP but computer says Android. I have tried changing the USB /VID ID that reads off what is displayed in Device manager not sure if I did it right running myself crazy really, read HRS of Android info Im a noob but a fast learner especially if I get a little bit of guidance. I have tried doing every and all factory hard resets tried different flash tools probably didnt work because my computer doesnt display the correct model. Im trying to learn python at the very moment new to all of this have only hrs of experience of this all. Somebody plz be ever so kind to help me out, thanks!
Device-State:Recovery/Bootloader
Ellipsis 8
QTAQZ3
Vendor:Verizon Wireless
Build:KTO49
4.2KitKat
samson716 said:
Hello everyone, I have a tablet that is stuck in recovery and looks to me ADB is going to be the only way out here. Problem is ADB isnt recognizing my device, device manager named it MTP but computer says Android. I have tried changing the USB /VID ID that reads off what is displayed in Device manager not sure if I did it right running myself crazy really, read HRS of Android info Im a noob but a fast learner especially if I get a little bit of guidance. I have tried doing every and all factory hard resets tried different flash tools probably didnt work because my computer doesnt display the correct model. Im trying to learn python at the very moment new to all of this have only hrs of experience of this all. Somebody plz be ever so kind to help me out, thanks!
?
Click to expand...
Click to collapse
You want help with a device but you don't tell us any kind of information about your device, how smart was that? What you need and how to do it can depend on what device model number you have.
Sent from my SM-S903VL using Tapatalk
SORRY
Droidriven said:
You want help with a device but you don't tell us any kind of information about your device, how smart was that? What you need and how to do it can depend on what device model number you have.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Not very smart at all sorry about that! I didnt disclose that, reason being the research i have done everybod turns there head when this crap device is mentioned. Yes I agree not worth time and energy but already invested so much time its worth it to me and also i have.
Ellipsis8
QTAQZ3/4.2Jellybean/KTO49
samson716 said:
Not very smart at all sorry about that! I didnt disclose that, reason being the research i have done everybod turns there head when this crap device is mentioned. Yes I agree not worth time and energy but already invested so much time its worth it to me and also i have.
Ellipsis8
QTAQZ3
4.2Kitkat
KTO49
Thanks!
Click to expand...
Click to collapse
samson716 said:
samson716 said:
Not very smart at all sorry about that! I didnt disclose that, reason being the research i have done everybod turns there head when this crap device is mentioned. Yes I agree not worth time and energy but already invested so much time its worth it to me and also i have.
Ellipsis8
QTAQZ3
4.2Kitkat
KTO49
Thanks!
Click to expand...
Click to collapse
are you using stock recovery or a custom recovery?
Click to expand...
Click to collapse
ayu321 said:
samson716 said:
are you using stock recovery or a custom recovery?
Click to expand...
Click to collapse
Stock
Click to expand...
Click to collapse
samson716 said:
ayu321 said:
Stock
Click to expand...
Click to collapse
Can you please tell me that what caused this problem ? what were you doing with the device? flashing roms ?
Click to expand...
Click to collapse
ayu321 said:
samson716 said:
Can you please tell me that what caused this problem ? what were you doing with the device? flashing roms ?
Click to expand...
Click to collapse
No I was literally doing nothing I was actually flashing my Samsung Device at that moment. From what I remember it occurred when I noticed at update to marshmallow updated then rebooted it. Ever since its been in this bootloop! Im not trying to root it put a custom rom on it just want it to function nothing special.
Click to expand...
Click to collapse
samson716 said:
ayu321 said:
No I was literally doing nothing I was actually flashing my Samsung Device at that moment. From what I remember it occurred when I noticed at update to marshmallow updated then rebooted it. Ever since its been in this bootloop! Im not trying to root it put a custom rom on it just want it to function nothing special.
Click to expand...
Click to collapse
You have soft bricked your phone . The only way to fix it is it flash its stock rom. If you are new to this stuff I would suggest you to read this article carefully and if you have any doubts , ask me.
https://www.maketecheasier.com/android-root-custom-recovery-and-roms/
Click to expand...
Click to collapse
samson716 said:
Hello everyone, I have a tablet that is stuck in recovery and looks to me ADB is going to be the only way out here. Problem is ADB isnt recognizing my device, device manager named it MTP but computer says Android. I have tried changing the USB /VID ID that reads off what is displayed in Device manager not sure if I did it right running myself crazy really, read HRS of Android info Im a noob but a fast learner especially if I get a little bit of guidance. I have tried doing every and all factory hard resets tried different flash tools probably didnt work because my computer doesnt display the correct model. Im trying to learn python at the very moment new to all of this have only hrs of experience of this all. Somebody plz be ever so kind to help me out, thanks!
Device-State:Recovery/Bootloader
Ellipsis 8
QTAQZ3
Vendor:Verizon Wireless
Build:KTO49
4.2KitKat
Click to expand...
Click to collapse
Where did this problem start? Did you cause this by modifying, attempting to root or flashing the device with something that caused this?
If so, about your only option is to use your device's flashtool to flash the stock firmware. If your device's stock firmware isn't available then you might be out of luck repairing your device. If this is the case then your only other option might be getting someone that has a device exactly like yours that is rooted and getting them to pull copies of the various .img files needed for your device then using adb shell to dd those .img files on your device. But, to be honest, I don't think this is gonna happen for you. You probably will have to take the device to a repair shop. It will probably be cheaper to just buy another tablet because the cost of repair will probably be more than what you paid for the device.
Sent from my SM-S903VL using Tapatalk
ayu321 said:
samson716 said:
You have soft bricked your phone . The only way to fix it is it flash its stock rom. If you are new to this stuff I would suggest you to read this article carefully and if you have any doubts , ask me.
https://www.maketecheasier.com/android-root-custom-recovery-and-roms/
Click to expand...
Click to collapse
Okay not sure which Flash tool to use nor get my stock rom I dread to say but i dont think there is one available. Its a generic tablet its made by Quanta. Not sure how to put it in a download mode either I assume ADB is the only way to transfer any files.
Click to expand...
Click to collapse
Your device probably uses SPFlashtool or fastboot.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Where did this problem start? Did you cause this by modifying, attempting to root or flashing the device with something that caused this?
If so, about your only option is to use your device's flashtool to flash the stock firmware. If your device's stock firmware isn't available then you might be out of luck repairing your device. If this is the case then your only other option might be getting someone that has a deuce exactly like yours that is rooted and getting them to pull copies of the various .img files needed for your device then using adb shell to dd those .img files on your device. But, to be honest, I don't think this is gonna happen for you. You probably will have to take the device to a repair shop. It will probably be cheaper to just buy another tablet because the cost of repair will probably be more than what you paid for the device.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Its pretty easy to fix a soft bricked device , even if stock rom isnt available , any rom compatible with his device can fix the issue .
ayu321 said:
Its pretty easy to fix a soft bricked device , even if stock rom isnt available , any rom compatible with his device can fix the issue .
Click to expand...
Click to collapse
To be compatible, the ROM typically has to be ported and that usually requires the stock firmware or stock source from the device that the ROM is being ported over to. 99% of the time you can't just flash a ROM from a different model number, even if the CPU is the same, there's quite a bit more to it than that. The android operating system is built for the specific hardware it is installed on, the two devices would have to be exactly the same and have the exact same components, any differences in hardware make he firmwares incompatible.
For this particular device, I doubt the stock firmware or stock source code area available, even if it were, porting another ROM wouldn't be necessary because if it were available it could just be flashed with that instead of porting a ROM.
About the only time a ROM from a different model number can be used without any porting or edits being made is when the devices are exactly the same device just rebranded with a different "name".
But thanks for trying to tell me something that you thought I didn't know, now it seems I've told you something that you didn't know.
Sent from my SM-S903VL using Tapatalk
samson716 said:
ayu321 said:
Okay not sure which Flash tool to use nor get my stock rom I dread to say but i dont think there is one available. Its a generic tablet its made by Quanta. Not sure how to put it in a download mode either I assume ADB is the only way to transfer any files.
Click to expand...
Click to collapse
1.Search for your tablet's root package , download it and move it to your tablet's sd card. Then enter your recovery mode by pressing power button+ Home button+ Volume button at same time for 10sec. Once entered , go to option "apply update from sd card" and select the root package you downloaded. (CONGRATS YOU HAVE ROOTED YOUR PHONE!)
2.Search for your tablet's 'custom recovery' , download it and flash it through odin tool(pc) .
3.Final Step ! BASED ON THE RECOVERY YOU FLASHED THESE STEPS MAY DIFFER , SO REPLY ME IF YOU SUCCEED IN FLASHING CUSTOM RECOVERY
Click to expand...
Click to collapse
ayu321 said:
1.Search for your tablet's root package , download it and move it to your tablet's sd card. Then enter your recovery mode by pressing power button+ Home button+ Volume button at same time for 10sec. Once entered , go to option "apply update from sd card" and select the root package you downloaded. (CONGRATS YOU HAVE ROOTED YOUR PHONE!)
2.Search for your tablet's 'custom recovery' , download it and flash it through odin tool(pc) .
3.Final Step ! BASED ON THE RECOVERY YOU FLASHED THESE STEPS MAY DIFFER , SO REPLY ME IF YOU SUCCEED IN FLASHING CUSTOM RECOVERY
Click to expand...
Click to collapse
Odin is for Samsung devices, not other devices.
The device they are repairing is not a Samsung device. They have this device and a Samsung device. The issue on this device occurred while they were in the process of flashing their Samsung device.
I know you're trying to help but don't post anything unless you are absolutely certain that you know what you're talking about.
In this case, you didn't and that can easily lead to a hard bricked device because they followed your instruction.
Stick to answering questions about devices you personally have dealt with, don't go assuming that you understand someone else's device. They are all different, the methods, tricks and tools for one won't necessarily work on another.
You understand android somewhat but judging by your posts, you don't understand the differences in devices and methods. But you will after you've been here a while.
Sent from my SM-S903VL using Tapatalk
---------- Post added at 10:39 PM ---------- Previous post was at 10:32 PM ----------
DO NOT USE ODIN ON YOUR DEVICE!!!
Odin is only for Samsung devices.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Where did this problem start? Did you cause this by modifying, attempting to root or flashing the device with something that caused this?
If so, about your only option is to use your device's flashtool to flash the stock firmware. If your device's stock firmware isn't available then you might be out of luck repairing your device. If this is the case then your only other option might be getting someone that has a device exactly like yours that is rooted and getting them to pull copies of the various .img files needed for your device then using adb shell to dd those .img files on your device. But, to be honest, I don't think this is gonna happen for you. You probably will have to take the device to a repair shop. It will probably be cheaper to just buy another tablet because the cost of repair will probably be more than what you paid for the device.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
thankyou so much for the fast responses much appreciated to take your time to explain. Okay i have a question what would be the course of detailed action to preform getting any and all missing .img's it may need. Also i know its a crazy question but would i be able to preform this in store with the displayed tablet that matches mine? How difficult is something like this, and is there any other methods at all I can try to boot past this bootloader. And now that i remember correctly from reading others this happened when I upgraded to 5.1 or 5.0 thank you everybody once again!
samson716 said:
thankyou so much for the fast responses much appreciated to take your time to explain. Okay i have a question what would be the course of detailed action to preform getting any and all missing .img's it may need. Also i know its a crazy question but would i be able to preform this in store with the displayed tablet that matches mine? How difficult is something like this, and is there any other methods at all I can try to boot past this bootloader. And now that i remember correctly from reading others this happened when I upgraded to 5.1 or 5.0 thank you everybody once again!
Click to expand...
Click to collapse
No, you wouldn't be able to get it from a tablet in the store, it's a rather involved process that requires connecting the device to PC, it also requires rooting the device and flashing a custom recovery, and that's all before you actually get to where you can pull the files. It'll take a couple of hours,or more to do it.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
No, you wouldn't be able to get it from a tablet in the store, it's a rather involved process that requires connecting the device to PC, it also requires rooting the device and flashing a custom recovery, and that's all before you actually get to where you can pull the files. It'll take a couple of hours,or more to do it.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Is there absolutely anything i can try, just a long shot in the dark?
samson716 said:
Is there absolutely anything i can try, just a long shot in the dark?
Click to expand...
Click to collapse
The only other option is pretty risky. You can try a firmware from another device that has the same CPU and hardware as your device, you'd have to compare specs. It would have to have the same CPU, same screen resolution, same camera(front and rear), same amount of RAM, same amount of internal storage, same accelerometers, etc.. It has to have all the same components that yours has.
Sent from my SM-S903VL using Tapatalk
I do have experience flashing phones. I don't need help with adb and fastboot.
I am just confused at to what exactly TWRP is? Is that the recovery? What should I flash to my phone?
Either way, I just want to root my phone and install a custom rom to it...but I don't see many or any custom roms except for TWRP...so really just want root above all else
Please tell me what I need to do and in what order...lol.....thank you
ImIntoStuff said:
I do have experience flashing phones. I don't need help with adb and fastboot.
I am just confused at to what exactly TWRP is? Is that the recovery? What should I flash to my phone?
Either way, I just want to root my phone and install a custom rom to it...but I don't see many or any custom roms except for TWRP...so really just want root above all else
Please tell me what I need to do and in what order...lol.....thank you
Click to expand...
Click to collapse
TWRP is custom recovery. It's still in beta.
As far as I know, there are no custom roms. 8.1 is too new and they are still working on things.
Root with Magisk. Plenty of how to threads.
Sent from my Pixel 2 using Tapatalk
ImIntoStuff said:
I do have experience flashing phones. I don't need help with adb and fastboot.
I am just confused at to what exactly TWRP is? Is that the recovery? What should I flash to my phone?
Either way, I just want to root my phone and install a custom rom to it...but I don't see many or any custom roms except for TWRP...so really just want root above all else
Please tell me what I need to do and in what order...lol.....thank you
Click to expand...
Click to collapse
Diesel_Jeremiah said:
TWRP is custom recovery. It's still in beta.
As far as I know, there are no custom roms. 8.1 is too new and they are still working on things.
Root with Magisk. Plenty of how to threads.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
TWRP actually just came out of beta with 12/12 Walleye(12/14 Taimen) build, hopefully there will be some custom roms soon... You can use the Skipsoft Android toolkit to root, unlock, flash twrp etc. Or do it manually following guides here on XDA under development section https://forum.xda-developers.com/pixel-2/development, ADB has been updated so make sure to have the latest platform tools.
Currently theres no custom ROMs at all for Pixel 2.
TWRP is a recovery.
Rooting is pretty straight-forward I studied these 2 articles/thread:
http://highonandroid.com/android-smartphones/how-to-root-pixel-2-or-pixel-2-xl-easiest-method/
https://forum.xda-developers.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417
The kind of confusing part is when you want to change custom kernels and update TWRP.
As the recovery, kernel and root stuff all play around in the same partition now.
Read around the forum, since you got experience you will figure it out.
bland.life said:
Currently theres no custom ROMs at all for Pixel 2.
TWRP is a recovery.
Rooting is pretty straight-forward I studied these 2 articles/thread:
http://highonandroid.com/android-smartphones/how-to-root-pixel-2-or-pixel-2-xl-easiest-method/
https://forum.xda-developers.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417
The kind of confusing part is when you want to change custom kernels and update TWRP.
As the recovery, kernel and root stuff all play around in the same partition now.
Read around the forum, since you got experience you will figure it out.
Click to expand...
Click to collapse
Ok I have TWRP installed and have it rooted, because root checker confirmed it.
I am currently installing busybox, not even sure why but I think I want it. Anyone want to tell me what it is specifically for? Also the app runs, says installing busybox and just hangs forever. Currently trying to let the smart install do it's thing and not move focus away from the busybox installing page
ImIntoStuff said:
Ok I have TWRP installed and have it rooted, because root checker confirmed it.
I am currently installing busybox, not even sure why but I think I want it. Anyone want to tell me what it is specifically for? Also the app runs, says installing busybox and just hangs forever. Currently trying to let the smart install do it's thing and not move focus away from the busybox installing page
Click to expand...
Click to collapse
Oh, and android reports a problem with called "Android System - There's an internal problem with your device. Contact your manufacturer for details."
What is causing that to be reported every time I restart?
ImIntoStuff said:
Ok I have TWRP installed and have it rooted, because root checker confirmed it.
I am currently installing busybox, not even sure why but I think I want it. Anyone want to tell me what it is specifically for? Also the app runs, says installing busybox and just hangs forever. Currently trying to let the smart install do it's thing and not move focus away from the busybox installing page
Click to expand...
Click to collapse
Oh, and android reports a problem with called "Android System - There's an internal problem with your device. Contact your manufacturer for details."
What is causing that to be reported every time I restart?
ImIntoStuff said:
Oh, and android reports a problem with called "Android System - There's an internal problem with your device. Contact your manufacturer for details."
What is causing that to be reported every time I restart?
Click to expand...
Click to collapse
Pretty sure that is the same for everyone according to the reading I've done. I'm looking to do the same with mine. What method did you use? Any snags?
Sent from my Pixel 2 using Tapatalk
Tucker204 said:
Pretty sure that is the same for everyone according to the reading I've done. I'm looking to do the same with mine. What method did you use? Any snags?
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Oh..so the android system error always happens? Ok..it does not seem to affect anything.
I used the Skipsoft package, which does all the things. Couple snags, it only wanted to accept the beta of magisk.
I'm thinking I got it all right now. I will report back if I find a problem
Tucker204 said:
Pretty sure that is the same for everyone according to the reading I've done. I'm looking to do the same with mine. What method did you use? Any snags?
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
So rooting your Pixel 2 will invariably trigger this error message on boot, for any user?
Are there other undesirable side effects to rooting your Pixel 2 at the moment?
Thanks
Hi guys, i've recently built a RR Oreo ROM for U Ultra without this device in hand.
just wanted to know if anyone wants to give it a shot, sources i used are based on HTC 10 sources, and just a blind build so i'm not responsible for any result,
all credits goes to HTC 10 (pme) developers, need to know if it's working (at least for booting)? then i will probably make further digging, thanks.
here is the LINK:
RR-Oreo for Oce (ported from pme)
Development Thread: https://forum.xda-developers.com/u-ultra/development/rom-resurrection-remix-os-t3848419
Nice!
I will get an U Ultra in the next days..
Already thought about porting LOS myself, but still a bit unsure if it will be worth the efforts..
Will test your ROM and report back when i have the phone on hand.
Siluxsept said:
Nice!
I will get an U Ultra in the next days..
Already thought about porting LOS myself, but still a bit unsure if it will be worth the efforts..
Will test your ROM and report back when i have the phone on hand.
Click to expand...
Click to collapse
Yeah, this device seems to be too unpopular, and this might get trouble for flashing, i can build a new one if you want to test it, thank you.
BTW, this ROM is built for dual sim variant.
Updated.
tarkzim said:
BTW, this ROM is built for dual sim variant.
Click to expand...
Click to collapse
I believe i'll get the single SIM variant, but not 100% sure.. Will see when my device arrives tomorrow or on thursday.
Right now I'm preparing my build environment for LOS. Which vendor blobs are you using, the PME ones in your vendor_htc repo?
Siluxsept said:
I believe i'll get the single SIM variant, but not 100% sure.. Will see when my device arrives tomorrow or on thursday.
Right now I'm preparing my build environment for LOS. Which vendor blobs are you using, the PME ones in your vendor_htc repo?
Click to expand...
Click to collapse
i'm based on pme ones, but preparing proper ocedugl blobs, not pushed yet.
Nice! Hope Ultra have more rom.
haven't see any feedback here, but i guess it might not booting with newer build, not even flashing with older build,
well, who knows, maybe there is miracle happening, hope if some have already tried it pleases let me know
tarkzim said:
haven't see any feedback here, but i guess it might not booting with newer build, not even flashing with older build,
well, who knows, maybe there is miracle happening, hope if some have already tried it pleases let me know
Click to expand...
Click to collapse
If it's single SIM I will try if not nope sorry
Plus will this brick our device
panda968 said:
If it's single SIM I will try if not nope sorry
Plus will this brick our device
Click to expand...
Click to collapse
for now its built for dual sim variant, cuz i don't have stock single variant Oreo rom dump, and it "shouldn't" brick your device, so backup your current ROM and if you want to help me you can provide your Oreo backup for me, thanks.
tarkzim said:
for now its built for dual sim variant, cuz i don't have stock single variant Oreo rom dump, and it "shouldn't" brick your device, so backup your current ROM and if you want to help me you can provide your Oreo backup for me, thanks.
Click to expand...
Click to collapse
Does it not matter that the processors are different? SD820 v SD821?
spikey001 said:
Does it not matter that the processors are different? SD820 v SD821?
Click to expand...
Click to collapse
i guess its fine.
tarkzim said:
for now its built for dual sim variant, cuz i don't have stock single variant Oreo rom dump, and it "shouldn't" brick your device, so backup your current ROM and if you want to help me you can provide your Oreo backup for me, thanks.
Click to expand...
Click to collapse
My device arrived today. I'll test your ROM and provide my stock backup over the weekend.
Siluxsept said:
My device arrived today. I'll test your ROM and provide my stock backup over the weekend.
Click to expand...
Click to collapse
thank you so much, i'm doing this only on my free time and not have this device lol, it'd be great if you can help me with it.
tarkzim said:
thank you so much, i'm doing this only on my free time and not have this device lol, it'd be great if you can help me with it.
Click to expand...
Click to collapse
Hi Tarkzim,
just created an untouched stock backup from TWRP. Is TWRP format okay or shall i convert it into boot.img / system.img?
Siluxsept said:
Hi Tarkzim,
just created an untouched stock backup from TWRP. Is TWRP format okay or shall i convert it into boot.img / system.img?
Click to expand...
Click to collapse
my old TWRP backups can be extracted as a zip file so i think it's ok.
Just tested to flash your ROM on my single SIM device. As you expected it refused to install on htc_oceuhl. updater script doesn't detect it as supported device.
What exactly we need from stock image to adjust for single SIM variant?
Siluxsept said:
Just tested to flash your ROM on my single SIM device. As you expected it refused to install on htc_oceuhl. updater script doesn't detect it as supported device.
What exactly we need from stock image to adjust for single SIM variant?
Click to expand...
Click to collapse
yeah. it won't pass the device check, but edit updater script manually will let you bypass it.
we need to see what libs or property values are different from dual sim variant.
tarkzim said:
yeah. it won't pass the device check, but edit updater script manually will let you bypass it.
we need to see what libs or property values are different from dual sim variant.
Click to expand...
Click to collapse
Yes i tried that.
It's failing to apply system image:
Patching system image unconditionally...
E1001: Failed to update system image.
Updater process ended with ERROR: 7
Changed updater script
Code:
.... package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat");
Now script succeeded, but nothing got installed.
Stock backup upload is running, will be ready in appr. 4 hours